Crush

Glamourous agentic coding for all 💘

Coding Agents Go Grade B Listed NOASSERTION Source-available
65.3/100
Rank #254 of 1316
Compare Crush

Promising trust profile, but some evidence still deserves review.

Open compare tool Suggest correction
Listing state
Listed
Evidence coverage
Grade C · 2/5 signals
Last push
2026-08-27 · 0d ago
Recent change
Rank +2

Is Crush safe? Crush scores 65.3/100 (Grade B), ranked #254 of 1316 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; 56% of recent commits are signed; last pushed 2026-08-27. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in Coding Agents

Quick Trust Read

What Would Improve It
Publish package provenance or release attestations for stronger supply-chain evidence.
Recent Changes
2026-08-26
Rank Moved
Rank dropped 26 spots (#224 → #250)
2026-08-24
Rank Moved
Rank dropped 15 spots (#211 → #226)
2026-08-22
Rank Moved
Rank rose 17 spots (#229 → #212)
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 6.9/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.
92.2
Activity sub-score · out of 100
#19

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 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 refreshed 2026-08-27 14:03 UTC · Repo last pushed today

Rank Trend

2026-08-11 2026-08-27

Activity & Reach

Stars
27.7k
Forks
2.2k
Last Push
2026-08-27
today
Commits (4 wk)
158
Downloads (7d)
HN mentions (30d)
Open Issues
403
Rank Change
▼4
was #250

Analysis

HVTrust Dimensions vs Coding Agents

65.3 / 100 · 100.0% confidence

Crush Coding Agents average (70 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
11.4 / 25
3.5 above avg 7.9
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
0.8 below avg 11.6
Transparency50% declared license · 50% OSSF Scorecard
14.4 / 17
3.1 above avg 11.3
Maintenance60% last-push freshness · 40% commit activity
20.0 / 20
5.2 above avg 14.8
AdoptionLog-scaled stars · package downloads
10.7 / 20
1.6 below avg 12.3

Activity Inputs

92.2 / 100
StarsRepository reach
26.7 / 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 Aug 25, 2026
Signed Commits
56%
of last 100 commits verified
Binary-Artifacts 10
Branch-Protection 3
CI-Tests 10
CII-Best-Practices 0
Code-Review 3
Contributors 10
Dangerous-Workflow 10
Dependency-Update-Tool 10
Fuzzing 0
License 9
Maintained 10
Packaging 10
Pinned-Dependencies 6
SAST 10
Security-Policy 10
Signed-Releases 8
Token-Permissions 0
Vulnerabilities 6

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?
56% 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.

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
medium confidence
Implemented
Crush appears to expose MCP server capabilities.
Detailed evidence is not shown in the public view.
External Service Dependencies
high confidence
8 detected
Public provider/service dependencies detected.
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
How this surface has changed

Detected changes to Crush'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-17
Provider Added
Runtime surface grew — new detected provider dependencies: DeepSeek, Groq, OpenRouter

Maintain Crush?

For maintainers

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.

Reputation Timeline

Signal history
Rank 9Grade 2Listed 1Surface 1
2026-08-26
Rank Moved
Rank dropped 26 spots (#224 → #250)
2026-08-24
Rank Moved
Rank dropped 15 spots (#211 → #226)
2026-08-22
Rank Moved
Rank rose 17 spots (#229 → #212)
2026-08-19
Rank Moved
Rank dropped 14 spots (#216 → #230)
2026-08-17
Rank Moved
Rank rose 14 spots (#231 → #217)
2026-08-13
Rank Moved
Rank dropped 22 spots (#196 → #218)
2026-08-12
Rank Moved
Rank rose 13 spots (#209 → #196)
2026-08-08
Rank Moved
Rank dropped 38 spots (#166 → #204)
2026-07-21
Grade Changed
Trust grade B → C
2026-07-17
Provider Added
Runtime surface grew — new detected provider dependencies: DeepSeek, Groq, OpenRouter
2026-07-16
Grade Changed
Trust grade C → B
2026-07-16
Rank Moved
Rank rose 20 spots (#161 → #141)
2026-07-13
Newly Listed
First tracked at rank #153

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 65.3 Grade B
Markdown:
[![HVTrust](https://hvtracker.net/badge/crush.svg)](https://hvtracker.net/agents/crush)
HTML:
<a href="https://hvtracker.net/agents/crush"><img src="https://hvtracker.net/badge/crush.svg" alt="HVTrust"></a>

Other agents in Coding Agents

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