Is Claude Code safe?
Claude Code scores 65.3/100 (Grade B), ranked #119 of 328 tracked open-source AI agent projects, on evidence coverage A (5 of 5 independent signal types).
The public evidence: no package-provenance attestation found;
OSSF Scorecard rates its supply-chain practices 5.5/10;
18% of recent commits are signed;
last pushed 2026-07-11. Every point is earned from checkable signals — never paid placement. How scoring works →
Active listing, but review is needed
[4.1.1] no declared license (GitHub license field is null)
Quick Trust Read
Verdict
Promising trust profile, but some evidence still deserves review.
65.3/100 · Grade B
Strongest Signal
Adoption
20.0/20
Weakest Signal
Transparency
4.7/17
What Would Improve It
Publish package provenance or release attestations for stronger supply-chain evidence.
Recent Changes
2026-07-04
Provider Removed
Runtime surface shrank — no longer detected: Anthropic
2026-06-24
Rank Moved
Rank dropped 13 spots (#150 → #163)
Maintainer Checklist
Declare an open licensePublish a clear OSI-approved license so usage and maintenance terms are independently verifiable.
Raise Scorecard signalsCurrent OSSF Scorecard is 5.5/10. Tighten the weakest checks to improve public safety evidence.
Publish provenanceAdd package provenance or release attestations so users can verify where shipped artifacts came from.
Increase signed commitsRaise the share of verified-signed commits to make maintainer identity and release history easier to trust.
Review Flags
[4.1.1] no declared license (GitHub license field is null)
How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption. Grade B reflects the trust score band: A ≥ 80, B ≥ 65, C ≥ 50, D < 50. Evidence coverage A is separate — it grades how many independent signal types back the score (5 of 5), so a high score on thin evidence stays visible. Full methodology →
Signals refreshed2026-07-11 04:00 UTC·Repo last pushed today
Rank Trend
2026-07-052026-07-11
Activity & Reach
Stars
137.3k
Forks
22.2k
Last Push
2026-07-11
today
Commits (4 wk)
36
Downloads (7d)
11,482,894
npm
HN mentions (30d)
582
Open Issues
10381
Rank Change
▲2
was #121
Analysis
HVTrust Dimensions
65.3 / 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.3 / 20
AdoptionStars and downloads
20.0 / 20
Activity Inputs
94.6 / 100
StarsRepository reach
30 / 30
FreshnessLast push recency
25.0 / 25
ActivityRecent commits
19.6 / 25
CommunityFork signal
20 / 20
Supply Chain Trust
Package Provenance
None
No package attestations found
OSSF Scorecard
5.5 / 10
OpenSSF Scorecard · scanned Jul 10, 2026
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.
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
None detected
No clear third-party provider dependency detected.
Credential signal:
No explicit API-key/config marker detected.
Tool / Plugin Surface
medium confidence
Declared
Declared plugin/integration surface detected.
Detailed evidence is not shown in the public view.
Package Provenance Drift
high confidence
Match
Published package metadata matches the tracked repo
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 Claude Code'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-07-04
Provider Removed
Runtime surface shrank — no longer detected: Anthropic
Runtime surface grew — new detected provider dependency: Anthropic
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.
Reputation Timeline
2026-07-04
Provider Removed
Runtime surface shrank — no longer detected: Anthropic
