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. Full methodology →
Signals refreshed2026-06-04 18:04 UTC·Repo last pushed yesterday
Rank Trend
2026-05-252026-06-04
Activity & Reach
Stars
130.0k
Forks
21.1k
Last Push
2026-06-03
yesterday
Commits (4 wk)
42
Downloads (7d)
9,738,911
npm
HN mentions (30d)
560
Open Issues
8428
Rank Change
▲21
was #135
Analysis
HVTrust Dimensions
61.8 / 100 · 100.0% confidence
Safety / IntegrityOSSF, provenance, signatures
7.8 / 25
Identity / ProvenanceListing and build link
10.8 / 18
TransparencyLicense and public checks
4.7 / 17
MaintenanceFreshness and commits
18.5 / 20
AdoptionStars and downloads
20.0 / 20
Activity Inputs
95.4 / 100
StarsRepository reach
30 / 30
FreshnessLast push recency
24.9 / 25
ActivityRecent commits
20.4 / 25
CommunityFork signal
20 / 20
Supply Chain Trust
Package Provenance
None
No package attestations found
OSSF Scorecard
5.5 / 10
via deps.dev · OpenSSF
Signed Commits
18%
of last 100 commits verified
Binary-Artifacts10
Branch-Protection5
CI-Tests2
CII-Best-Practices0
Code-Review1
Contributors10
Dangerous-Workflow10
Dependency-Update-Tool0
Fuzzing0
License9
Maintained10
Packaging-1
Pinned-Dependencies3
SAST0
Security-Policy10
Signed-Releases8
Token-Permissions0
Vulnerabilities10
Is Claude Code safe?
Proprietary software. A lower HVTrust score reflects fewer public supply-chain artifacts (open license, build provenance, signed commits) — not a security finding. Claude Code may have internal security practices not visible through public signals.
Claude Code 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 Claude Code publish package provenance?
No published build provenance is currently detected for Claude Code. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.
Does Claude Code have an OpenSSF Scorecard?
Claude Code has an OpenSSF Scorecard score of 5.5/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 Claude Code actively maintained?
Actively maintained. The repository was pushed to within the last 1 day(s).
What license does Claude Code use?
Claude Code ships under no SPDX license detected. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are Claude Code's commits signed?
18% of the last 100 commits to Claude Code 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.
Runtime trust — coming soon
HVTrust currently scores supply-chain signals. We're adding runtime trust next: what an agent actually does when it runs — what it can reach, which tools it carries, what external services it depends on. Track progress on the roadmap →
MCP support
Tool / plugin surface
External service deps
Package provenance drift
Maintain Claude Code?
HVTrust scores Claude Code 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.
Action counts reflect activity on public repos where this agent left detectable fingerprints.
Private repo usage is invisible. Counts are approximate (GitHub Search API caps at 1,000 results per query).
Methodology described in the Provenance Profile spec.
