How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption. Grade D 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-09 20:05 UTC·Repo last pushed 3 days ago
Activity & Reach
Stars
3.2k
Forks
395
Last Push
2026-07-06
3 days ago
Commits (4 wk)
0?
Downloads (7d)
147
npm
HN mentions (30d)
—
Open Issues
15
Rank Change
NEW
Analysis
HVTrust Dimensions
30.1 / 100 · 67.0% confidence
Safety / IntegrityOSSF, provenance, signatures
4.2 / 25
Identity / ProvenanceListing and build link
10.8 / 18
TransparencyLicense and public checks
8.5 / 17
MaintenanceFreshness and commits
11.8 / 20
AdoptionStars and downloads
11.3 / 20
Activity Inputs
57.7 / 100
StarsRepository reach
21.0 / 30
FreshnessLast push recency
24.6 / 25
ActivityRecent commits
0.0 / 25
CommunityFork signal
12.1 / 20
Supply Chain Trust
Package Provenance
None
No package attestations found
OSSF Scorecard
—
Not available
Signed Commits
83%
of last 100 commits verified
Is Grok CLI safe?
Public trust evidence for Grok CLI is thin: several supply-chain signals are missing or weak. This does not mean the project is unsafe — it means an outside observer cannot easily verify the usual integrity checks. Treat with extra scrutiny.
Does Grok CLI publish package provenance?
No published build provenance is currently detected for Grok CLI. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.
Does Grok CLI have an OpenSSF Scorecard?
No OpenSSF Scorecard data is currently published for Grok CLI. Maintainers can enable the Scorecard GitHub Action to get a public score; without it, automated supply-chain hygiene is harder for outsiders to verify.
Is Grok CLI actively maintained?
Actively maintained. The repository was pushed to within the last 3 day(s).
What license does Grok CLI use?
Grok CLI ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are Grok CLI's commits signed?
83% of the last 100 commits to Grok CLI 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
medium confidence
Declared
MCP support appears present, but direct server implementation is less certain.
Detailed evidence is not shown in the public view.
External Service Dependencies
low confidence
None detected
No clear third-party provider dependency 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
low confidence
Unknown
Package source metadata is missing or inconclusive
Detailed evidence is not shown in the public view.
MCP signal live
External deps live
Tool / plugin surface live
Package provenance drift live
Maintain Grok CLI?
HVTrust scores Grok CLI 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) · npm Registry (downloads, provenance)
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.2 · Raw JSON
