updated 2026-10-08 04:16 UTC

Grok CLI

Repository by superagent-ai

An open-source coding agent for the Grok API

Coding Agents TypeScript Listed MIT

Is Grok CLI safe? Thin or incomplete trust evidence. Review carefully before production use.

OSSF Scorecard 3.0 / 10
Provenance None
Signed commits 83%
Last push 94d ago
Compare Grok CLI

How does it stack up against its Coding Agents neighbours?

Pick any agent to compare →
Suggest a correction

In detail: Grok CLI scores 46.5/100 (Grade D), ranked #1049 of 1346 tracked open-source AI agent projects, on evidence coverage B (3 of 5 independent signal types). The public evidence: no package-provenance attestation found; OSSF Scorecard rates its supply-chain practices 3.0/10; 83% of recent commits are signed; last pushed 2026-07-06. Every point is earned from checkable signals — never paid placement. How scoring works →

How Grok CLI could raise its score

Each line changes one public signal and recomputes with the live scoring function. The gains don't add up exactly, because the score is capped near the top.

Already done? Suggest a correctionAdd the trust badge

Chain of custody

Scanners check what the code says. This traces who ships Grok CLI and whether that has changed: from the source repository, through how changes are reviewed and released, to the package you install. These are the checks for OWASP ASI04 Agentic Supply Chain Vulnerabilities.

  1. Source Signed

    github.com/superagent-ai/grok-cli, MIT, last pushed 2026-07-06. 83% of the last 100 commits carry a verified signature, so changes trace to a verified account.

  2. Review and release Weak

    OpenSSF Scorecard rates the repository's practices 3.0/10 (scanned Oct 3, 2026). The checks that decide who can get a change released:

    • Code Review2
    • Branch Protection3
    • Signed Releases0
    • Dangerous Workflow10
    • Token Permissions0
    • Pinned Dependencies0
    All 18 Scorecard checks
    Binary-Artifacts 10
    Branch-Protection 3
    CI-Tests 10
    CII-Best-Practices 0
    Code-Review 2
    Contributors 3
    Dangerous-Workflow 10
    Dependency-Update-Tool 0
    Fuzzing 0
    License 10
    Maintained 0
    Packaging -1
    Pinned-Dependencies 0
    SAST 7
    Security-Policy 0
    Signed-Releases 0
    Token-Permissions 0
    Vulnerabilities 0

  3. Published packages Not linked

    • npm grok-dev No source link declared No build attestation

    Without a build attestation, nothing proves the published files were built from this repository.

Changes to this chain

No change to package provenance, package source links, Scorecard coverage or license in HVTracker's daily snapshots of Grok CLI.

Evidence behind this score

Coverage B: 3 of 5 independent evidence types found.

  • GitHub repository data
  • Package downloads
  • Supply-chain checks
  • Public actions (missing)
  • Community mentions (missing)

Verify this score yourself

Every build re-issues Grok CLI’s score as an Ed25519-signed credential, valid for 7 days. You can check it offline against HVTracker’s published key; if anyone changes a number after signing, verification fails.

Signed credential (JSON) How to verify

What this score doesn’t check

It covers who ships the code, not what the code does. It doesn’t read tool descriptions or prompts for injected instructions, watch runtime behaviour, or find bugs nobody has disclosed yet. For that, run a content scanner before you connect it, such as Cisco MCP Scanner or Snyk Agent Scan.

How Grok CLI compares in Coding Agents

  1. #56 OpenCursor 49.1 +2.6
  2. #57 Tabby 49.0 +2.5
  3. #58 Grok CLI 46.5 this agent
  4. #59 opencode 46.2 −0.3
  5. #60 HumanLayer 46.1 −0.4

Bars show each HVTrust score; the tick marks Grok CLI’s 46.5.

Where the 46.5 comes from

HVTrust dimensions vs the Coding Agents average

46.5 / 100 · 100.0% confidence

Grok CLI Coding Agents average (75 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
7.9 / 25
1.2 below avg 9.1
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
1.0 below avg 11.8
Transparency50% declared license · 50% OSSF Scorecard
11.1 / 17
0.8 below avg 11.9
Maintenance60% last-push freshness · 40% commit activity
5.7 / 20
9.1 below avg 14.8
AdoptionLog-scaled stars · package downloads
12.0 / 20
in line with avg 12.2

Quick Trust Read

What Would Improve It
Publish package provenance or release attestations for stronger supply-chain evidence.
Recent Changes
2026-10-04
Activity Went Stale
No commits for 90 days
2026-09-23
Rank Moved
Rank dropped 613 spots (#386 → #999)
2026-09-22
Rank Moved
Rank dropped 51 spots (#335 → #386)
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 3.0/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.
Refresh maintenance signals The repo was last pushed 94 days ago. Fresh activity helps separate stable projects from stale ones.
Compare with another agent Get email alerts for Grok CLI View Coding Agents Report missing data
45.6
Activity sub-score · out of 100
#58
In Coding Agents

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 B is separate — it grades how many independent signal types back the score (3 of 5), so a high score on thin evidence stays visible. Full methodology →

Signals refreshed 2026-10-08 04:16 UTC · Repo last pushed 94 days ago

Rank Trend

2026-09-29 2026-10-08

Activity & Reach

Stars
3.5k
Forks
424
Last Push
2026-07-06
94 days ago
Commits (4 wk)
0
Downloads (7d)
429
npm
HN mentions (30d)
—
Open Issues
18
Rank Change
▼3
was #1046

Analysis

Activity Inputs

45.6 / 100
StarsRepository reach
21.3 / 30
FreshnessLast push recency
11.9 / 25
ActivityRecent commits
0.0 / 25
CommunityFork signal
12.2 / 20

Common questions about Grok CLI

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?
Grok CLI has an OpenSSF Scorecard score of 3.0/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 Grok CLI actively maintained?
Slowing down. Last push was 94 days ago — keep an eye on whether activity resumes.
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.

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
Declared
MCP support appears present, but direct server implementation is less certain.
Detailed evidence is not shown in the public view.
External Service Dependencies
high confidence
1 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
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
How this surface has changed

Detected changes to Grok CLI'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-10-04
Activity Went Stale
No commits for 90 days

Maintain Grok CLI?

For maintainers

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.

Submit a correction → Add the trust badge

Reputation Timeline

Signal history
Rank 29Grade 1Stale 1
2026-10-04
Activity Went Stale
No commits for 90 days
2026-09-23
Rank Moved
Rank dropped 613 spots (#386 → #999)
2026-09-22
Rank Moved
Rank dropped 51 spots (#335 → #386)
2026-09-21
Rank Moved
Rank rose 657 spots (#992 → #335)
2026-09-09
Rank Moved
Rank dropped 11 spots (#954 → #965)
2026-09-08
Rank Moved
Rank dropped 15 spots (#939 → #954)
2026-09-07
Rank Moved
Rank dropped 31 spots (#908 → #939)
2026-09-06
Rank Moved
Rank dropped 11 spots (#897 → #908)
2026-09-05
Rank Moved
Rank dropped 56 spots (#841 → #897)
2026-09-04
Rank Moved
Rank dropped 37 spots (#804 → #841)
2026-09-03
Rank Moved
Rank dropped 48 spots (#756 → #804)
2026-09-02
Rank Moved
Rank dropped 36 spots (#720 → #756)
2026-09-01
Rank Moved
Rank dropped 34 spots (#686 → #720)
2026-08-31
Rank Moved
Rank dropped 37 spots (#649 → #686)
2026-08-30
Rank Moved
Rank dropped 18 spots (#631 → #649)
2026-08-29
Rank Moved
Rank dropped 41 spots (#590 → #631)
2026-08-28
Rank Moved
Rank dropped 18 spots (#572 → #590)
2026-08-27
Rank Moved
Rank dropped 15 spots (#557 → #572)
2026-08-26
Rank Moved
Rank dropped 84 spots (#473 → #557)
2026-08-24
Rank Moved
Rank dropped 15 spots (#458 → #473)
2026-08-22
Rank Moved
Rank rose 14 spots (#474 → #460)
2026-08-19
Rank Moved
Rank dropped 10 spots (#463 → #473)
2026-08-17
Rank Moved
Rank rose 10 spots (#471 → #461)
2026-08-14
Grade Changed
Trust grade C → D
2026-08-13
Rank Moved
Rank dropped 14 spots (#441 → #455)
2026-08-12
Rank Moved
Rank rose 11 spots (#452 → #441)
2026-08-10
Rank Moved
Rank dropped 15 spots (#437 → #452)
2026-08-08
Rank Moved
Rank dropped 109 spots (#324 → #433)
2026-07-15
Rank Moved
Rank dropped 18 spots (#259 → #277)
2026-07-14
Rank Moved
Rank dropped 14 spots (#245 → #259)
2026-07-13
Rank Moved
Rank dropped 30 spots (#215 → #245)
GitHub → npm: grok-dev

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 46.5 Grade D
Markdown:
[![HVTrust](https://hvtracker.net/badge/grok-cli.svg)](https://hvtracker.net/agents/grok-cli)
HTML:
<a href="https://hvtracker.net/agents/grok-cli"><img src="https://hvtracker.net/badge/grok-cli.svg" alt="HVTrust"></a>

Other agents in Coding Agents

Data sources
GitHub REST API (repo, commits, stars, forks, license) · npm Registry (downloads, provenance) · OpenSSF Scorecard CLI
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.4 · Raw JSON