Is Crush safe?
Crush scores 63.5/100 (Grade C), ranked #151 of 371 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.9/10;
42% of recent commits are signed;
last pushed 2026-07-13. Every point is earned from checkable signals — never paid placement. How scoring works →
Quick Trust Read
Verdict
Promising trust profile, but some evidence still deserves review.
63.5/100 · Grade C
Strongest Signal
Maintenance
20.0/20
Weakest Signal
Safety / Integrity
10.7/25
What Would Improve It
Publish package provenance or release attestations for stronger supply-chain evidence.
Recent Changes
2026-07-13
Newly Listed
First tracked at rank #151
Maintainer Checklist
Raise Scorecard signalsCurrent OSSF Scorecard is 6.9/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.
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 →
Signals refreshed2026-07-13 10:30 UTC·Repo last pushed today
Activity & Reach
Stars
26.5k
Forks
2.1k
Last Push
2026-07-13
today
Commits (4 wk)
140
Downloads (7d)
—
HN mentions (30d)
—
Open Issues
348
Rank Change
NEW
Analysis
HVTrust Dimensions
63.5 / 100 · 100.0% confidence
Safety / IntegrityOSSF, provenance, signatures
10.7 / 25
Identity / ProvenanceListing and build link
10.8 / 18
TransparencyLicense and public checks
14.4 / 17
MaintenanceFreshness and commits
20.0 / 20
AdoptionStars and downloads
10.6 / 20
Activity Inputs
92.0 / 100
StarsRepository reach
26.5 / 30
FreshnessLast push recency
25.0 / 25
ActivityRecent commits
25 / 25
CommunityFork signal
15.5 / 20
Supply Chain Trust
Package Provenance
None
No package attestations found
OSSF Scorecard
6.9 / 10
OpenSSF Scorecard · scanned Jul 12, 2026
Signed Commits
42%
of last 100 commits verified
Binary-Artifacts10
Branch-Protection3
CI-Tests10
CII-Best-Practices0
Code-Review2
Contributors10
Dangerous-Workflow10
Dependency-Update-Tool10
Fuzzing0
License9
Maintained10
Packaging10
Pinned-Dependencies6
SAST10
Security-Policy10
Signed-Releases8
Token-Permissions0
Vulnerabilities7
Is Crush safe?
Source-available software. A lower HVTrust score reflects fewer public supply-chain artifacts (open license, build provenance, signed commits) — not a security finding. Crush may have internal security practices not visible through public signals.
Crush 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 Crush publish package provenance?
No published build provenance is currently detected for Crush. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.
Does Crush have an OpenSSF Scorecard?
Crush has an OpenSSF Scorecard score of 6.9/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 Crush actively maintained?
Actively maintained. The repository was pushed to within the last 1 day(s).
What license does Crush use?
Crush ships under NOASSERTION. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are Crush's commits signed?
42% of the last 100 commits to Crush 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
low confidence
Declared
MCP support appears present, but direct server implementation is less certain.
Detailed evidence is not shown in the public view.
Credential signal:
API keys or service config markers documented.
Tool / Plugin Surface
None detected
No clear plugin system or broad tool 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
Maintain Crush?
HVTrust scores Crush 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.
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.2 · Raw JSON
