Is Brooks Lint safe to use?

Brooks Lint has an HVTrust score of 55.5/100 (Grade C), ranked #151 of 351 tracked AI agent projects. This score reflects verifiable supply-chain integrity, transparency, maintenance, and adoption signals.

What is the trust score for Brooks Lint?

Brooks Lint scores 55.5/100 on HVTracker's evidence-weighted HVTrust scale. It has 1.5k GitHub stars and is categorized under Agent Skills.

Brooks Lint

hyhmrright/brooks-lint

AI code reviews grounded in 12 classic engineering books — decay risk diagnostics with book citations, severity labels, and 6 analysis modes including full-sweep auto-fix

Agent Skills HTML Listed MIT

Is Brooks Lint safe? Promising trust profile, but some evidence still deserves review.

OSSF Scorecard 6.1 / 10

Provenance None

Signed commits 7%

Last push 5d ago

Compare Brooks Lint

How does it stack up against its Agent Skills neighbours?

Pick any agent to compare →

Suggest a correction

In detail: Brooks Lint scores 55.5/100 (Grade C), ranked #151 of 351 tracked open-source AI agent projects, on evidence coverage C (2 of 5 independent signal types). The public evidence: no package-provenance attestation found; OSSF Scorecard rates its supply-chain practices 6.1/10; 7% of recent commits are signed; last pushed 2026-09-21. Every point is earned from checkable signals — never paid placement. How scoring works →

How Brooks Lint compares in Agent Skills

Bars show each HVTrust score; the tick marks Brooks Lint’s 55.5.

Where the 55.5 comes from

HVTrust dimensions vs the Agent Skills average

55.5 / 100 · 100.0% confidence

Brooks Lint Agent Skills average (351 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits

8.0 / 25

in line with avg 8.1

Identity / Provenance60% listing status · 40% build provenance

10.8 / 18

0.6 below avg 11.4

Transparency50% declared license · 50% OSSF Scorecard

13.7 / 17

1.5 above avg 12.2

Maintenance60% last-push freshness · 40% commit activity

17.2 / 20

3.0 above avg 14.2

AdoptionLog-scaled stars · package downloads

7.6 / 20

1.4 below avg 9.0

Quick Trust Read

What Would Improve It

Publish package provenance or release attestations for stronger supply-chain evidence.

Recent Changes

2026-09-25

Grade Changed

Trust grade D → C

2026-09-25

Rank Moved

Rank rose 163 spots (#314 → #151)

2026-09-25

HVTrust Changed

HVTrust up 19.0pts (36.5 → 55.5)

Maintainer Checklist

Raise Scorecard signals Current OSSF Scorecard is 6.1/10. Tighten the weakest checks to improve public safety evidence.

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

69.3

Activity sub-score · out of 100

#151

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 C reflects the trust score band: A ≥ 80, B ≥ 65, C ≥ 50, D < 50. Evidence coverage C is separate — it grades how many independent signal types back the score (2 of 5), so a high score on thin evidence stays visible. Full methodology →

Rank Trend

2026-08-11 2026-09-26

Activity & Reach

Stars

1.5k

Forks

Last Push

2026-09-21

5 days ago

Commits (4 wk)

Downloads (7d)

—

HN mentions (30d)

—

Open Issues

Rank Change

was #151

Analysis

Activity Inputs

69.3 / 100

StarsRepository reach

19.1 / 30

FreshnessLast push recency

24.3 / 25

ActivityRecent commits

17.2 / 25

CommunityFork signal

8.6 / 20

Supply Chain Trust

Package Provenance

None

No package attestations found

OSSF Scorecard

6.1 / 10

OpenSSF Scorecard · scanned Sep 16, 2026

Signed Commits

of last 100 commits verified

Binary-Artifacts 10

Branch-Protection 3

CI-Tests 6

CII-Best-Practices 0

Code-Review 1

Contributors 0

Dangerous-Workflow 10

Dependency-Update-Tool 0

Fuzzing 0

License 10

Maintained 10

Packaging -1

Pinned-Dependencies 10

SAST 0

Security-Policy 10

Signed-Releases -1

Token-Permissions 9

Vulnerabilities 10

Common questions about Brooks Lint

Brooks Lint has a mixed signal profile. Some trust indicators are present, others are missing. Whether it is safe for your use case depends on which gaps matter to you — review the breakdown below before adopting in production.

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?

Brooks Lint has an OpenSSF Scorecard score of 6.1/10. The Scorecard checks for branch protection, signed releases, dependency updates, fuzzing, code review, and other supply-chain hygiene items. See the full check breakdown on this page.

Is Brooks Lint actively maintained?

Actively maintained. The repository was pushed to within the last 5 day(s).

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?

7% 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

N/A

No package source configured

Detailed evidence is not shown in the public view.

MCP signal live
External deps live
Tool / plugin surface live
Package provenance drift live

How this surface has changed

Detected changes to Brooks Lint's runtime surface and supply-chain posture, from daily public-signal snapshots. A change here means our detectors see something different — a genuinely changed capability, or better evidence of an existing one.

2026-09-23

Tool Surface Changed

Detected tool/plugin surface changed: none → declared

2026-09-23

Provider Added

Runtime surface grew — new detected provider dependencies: Anthropic, Google Gemini

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

2026-09-25

Grade Changed

Trust grade D → C

2026-09-25

Rank Moved

Rank rose 163 spots (#314 → #151)

2026-09-25

HVTrust Changed

HVTrust up 19.0pts (36.5 → 55.5)

2026-09-23

Tool Surface Changed

Detected tool/plugin surface changed: none → declared

2026-09-23

Provider Added

Runtime surface grew — new detected provider dependencies: Anthropic, Google Gemini

2026-09-23

Rank Moved

Rank dropped 77 spots (#236 → #313)

2026-09-23

HVTrust Changed

HVTrust up 4.0pts (32.5 → 36.5)

2026-09-22

Newly Listed

First tracked at rank #236

2026-09-21

Removed From Active Tracking

Removed from active tracking

2026-09-10

Rank Moved

Rank dropped 10 spots (#290 → #300)

2026-09-05

Rank Moved

Rank dropped 10 spots (#261 → #271)

2026-09-03

Rank Moved

Rank dropped 12 spots (#244 → #256)

2026-09-02

Rank Moved

Rank dropped 17 spots (#227 → #244)

2026-09-01

Rank Moved

Rank dropped 10 spots (#217 → #227)

2026-08-31

Rank Moved

Rank dropped 17 spots (#200 → #217)

2026-08-30

Rank Moved

Rank dropped 34 spots (#166 → #200)

2026-08-29

Rank Moved

Rank dropped 40 spots (#126 → #166)

2026-08-28

Rank Moved

Rank dropped 26 spots (#100 → #126)

2026-08-27

Rank Moved

Rank dropped 20 spots (#80 → #100)

2026-08-26

Scorecard Added

OSSF Scorecard: 6.0/10

2026-08-26

Rank Moved

Rank rose 68 spots (#148 → #80)

2026-08-26

HVTrust Changed

HVTrust up 20.1pts (15.8 → 35.9)

2026-08-16

Rank Moved

Rank dropped 11 spots (#137 → #148)

2026-08-11

Newly Listed

First tracked at rank #138

GitHub →

Embed Badge Badge guide for maintainers →

For maintainers

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) · OpenSSF Scorecard CLI
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.3 · Raw JSON