updated 2026-08-12 05:02 UTC

Brooks Lint

hyhmrright/brooks-lint

AI code reviews grounded in 12 classic engineering books — decay risk diagnostics with book citations, severity labels,

Agent Skills JavaScript Grade D Listed MIT
15.5/100
Rank #138 of 148
Compare Brooks Lint

How does it stack up against its Agent Skills neighbours?

Pick any agent to compare →

Thin or incomplete trust evidence. Review carefully before production use.

Open compare tool Suggest correction
Listing state
Listed
Evidence coverage
Grade D · 1/5 signals
Last push
2026-08-04 · 8d ago
Recent change
New

Is Brooks Lint safe? Brooks Lint scores 15.5/100 (Grade D), ranked #138 of 148 tracked open-source AI agent projects, on evidence coverage D (1 of 5 independent signal types). The public evidence: no package-provenance attestation found; no OSSF Scorecard result yet; 4% of recent commits are signed; last pushed 2026-08-04. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in Agent Skills

#136 Ktx — 16.6 (D) → #137 Claude Ads — 15.5 (D) → #139 GPT Image2 Skill — 15.3 (D) → #140 Claude Code Java — 15.1 (D) →

Quick Trust Read

What Would Improve It
Add or improve OSSF Scorecard coverage so safety checks are easier to verify.
Recent Changes
2026-08-11
Newly Listed
First tracked at rank #138
Maintainer Checklist
Add Scorecard coverage Expose the repository to OpenSSF Scorecard checks so supply-chain posture is easier to verify.
Publish provenance Add package provenance or release attestations so users can verify where shipped artifacts came from.
Increase signed commits Raise the share of verified-signed commits to make maintainer identity and release history easier to trust.
Compare with another agent Get email alerts for Brooks Lint View Agent Skills Report missing data
65.7
Activity sub-score · out of 100
#138
In Agent Skills

How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption. Grade D reflects the trust score band: A ≥ 80, B ≥ 65, C ≥ 50, D < 50. Evidence coverage D is separate — it grades how many independent signal types back the score (1 of 5), so a high score on thin evidence stays visible. Full methodology →

Signals refreshed 2026-08-12 05:02 UTC · Repo last pushed 8 days ago

Rank Trend

2026-08-11 2026-08-12

Activity & Reach

Stars
1.3k
Forks
60
Last Push
2026-08-04
8 days ago
Commits (4 wk)
14
Downloads (7d)
—
HN mentions (30d)
—
Open Issues
1
Rank Change
=
was #138

Analysis

HVTrust Dimensions vs Agent Skills

15.5 / 100 · 40.0% confidence

Brooks Lint Agent Skills average (148 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
0.2 / 25
2.5 below avg 2.7
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
0.5 below avg 11.3
Transparency50% declared license · 50% OSSF Scorecard
8.5 / 17
in line with avg 8.5
Maintenance60% last-push freshness · 40% commit activity
16.2 / 20
1.1 above avg 15.1
AdoptionLog-scaled stars · package downloads
7.5 / 20
1.7 below avg 9.2

Activity Inputs

65.7 / 100
StarsRepository reach
18.7 / 30
FreshnessLast push recency
23.9 / 25
ActivityRecent commits
14.7 / 25
CommunityFork signal
8.3 / 20

Supply Chain Trust

Package Provenance
None
No package attestations found
OSSF Scorecard
—
Not available
Signed Commits
4%
of last 100 commits verified

Is Brooks Lint safe?

Public trust evidence for Brooks Lint is thin: several supply-chain signals are missing or weak. This does not mean the project is unsafe — it means an outside observer cannot easily verify the usual integrity checks. Treat with extra scrutiny.
Does Brooks Lint publish package provenance?
No published build provenance is currently detected for Brooks Lint. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.
Does Brooks Lint have an OpenSSF Scorecard?
No OpenSSF Scorecard data is currently published for Brooks Lint. Maintainers can enable the Scorecard GitHub Action to get a public score; without it, automated supply-chain hygiene is harder for outsiders to verify.
Is Brooks Lint actively maintained?
Maintained. Last push was 8 days ago.
What license does Brooks Lint use?
Brooks Lint ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are Brooks Lint's commits signed?
4% of the last 100 commits to Brooks Lint are verified-signed (GPG, SSH, S/MIME, or GitHub's signing flow). Signed commits help confirm that code was authored by who the commit claims.

Not a safety endorsement. HVTracker describes what public signals show, not whether a project is safe for your use case. Run your own security review before adopting in production.

AI agent surface

MCP, providers, tool surface
Scored in HVTrust

These runtime-trust fields — detected from public repo docs and manifests — contribute a bounded adjustment to this project's HVTrust score alongside supply-chain evidence. The exact values each field can add or subtract are documented in the methodology → Compare this surface across every listed agent in the capability matrix →

MCP Server Support
None detected
No MCP server signal detected.
Detailed evidence is not shown in the public view.
External Service Dependencies
high confidence
2 detected
Public provider/service dependencies detected.
Credential signal: API keys or service config markers documented.
Tool / Plugin Surface
high confidence
Declared
Declared plugin/integration surface detected.
Detailed evidence is not shown in the public view.
Package Provenance Drift
low confidence
Unknown
Package source metadata is missing or inconclusive
Detailed evidence is not shown in the public view.
  • MCP signal live
  • External deps live
  • Tool / plugin surface live
  • Package provenance drift live

Maintain Brooks Lint?

For maintainers

HVTrust scores Brooks Lint from public signals only — we never contact maintainers first. If a signal is wrong, stale, or missing (provenance you publish, a Scorecard you run, signed releases), tell us and we'll review it. Corrections are public and tracked on GitHub.

Submit a correction → Add the trust badge

Reputation Timeline

Signal history
Listed 1
2026-08-11
Newly Listed
First tracked at rank #138
GitHub → npm: brooks-lint

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 15.5 Grade D
Markdown:
[![HVTrust](https://hvtracker.net/badge/brooks-lint.svg)](https://hvtracker.net/agents/brooks-lint)
HTML:
<a href="https://hvtracker.net/agents/brooks-lint"><img src="https://hvtracker.net/badge/brooks-lint.svg" alt="HVTrust"></a>

Other agents in Agent Skills

Data sources
GitHub REST API (repo, commits, stars, forks, license) · npm Registry (downloads, provenance)
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.3 · Raw JSON