Is Grok CLI safe to use?

Grok CLI has an HVTrust score of 48.9/100 (Grade D), ranked #459 of 1308 tracked AI agent projects. This score reflects verifiable supply-chain integrity, transparency, maintenance, and adoption signals.

What is the trust score for Grok CLI?

Grok CLI scores 48.9/100 on HVTracker's evidence-weighted HVTrust scale. It has 3.4k GitHub stars and is categorized under Coding Agents.

Grok CLI

superagent-ai/grok-cli

An open-source coding agent for the Grok API

Coding Agents TypeScript Grade D Listed MIT

48.9/100

Rank #459 of 1308

Compare Grok CLI

How does it stack up against its Coding Agents neighbours?

Pick any agent to compare →

Thin or incomplete trust evidence. Review carefully before production use.

Open compare tool Suggest correction

Listing state

Listed

Evidence coverage

Grade B · 3/5 signals

Last push

2026-07-06 · 49d ago

Recent change

Rank +2

Is Grok CLI safe? Grok CLI scores 48.9/100 (Grade D), ranked #459 of 1308 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 →

Ranked neighbours in Coding Agents

#38 Grok Build — 51.5 (C) → #39 HumanLayer — 49.0 (D) → #41 Roo Code — 48.5 (D) → #42 opencode — 46.0 (D) →

Quick Trust Read

What Would Improve It

Publish package provenance or release attestations for stronger supply-chain evidence.

Recent Changes

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)

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 49 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

51.7

Activity sub-score · out of 100

#40

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 →

Rank Trend

2026-08-11 2026-08-24

Activity & Reach

Stars

3.4k

Forks

422

Last Push

2026-07-06

49 days ago

Commits (4 wk)

Downloads (7d)

147

npm

HN mentions (30d)

—

Open Issues

Rank Change

▼1

was #458

Analysis

HVTrust Dimensions vs Coding Agents

48.9 / 100 · 100.0% confidence

Grok CLI Coding Agents average (70 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits

7.9 / 25

in line with avg 7.6

Identity / Provenance60% listing status · 40% build provenance

10.8 / 18

0.8 below avg 11.6

Transparency50% declared license · 50% OSSF Scorecard

11.1 / 17

in line with avg 11.1

Maintenance60% last-push freshness · 40% commit activity

8.7 / 20

6.2 below avg 14.9

AdoptionLog-scaled stars · package downloads

11.4 / 20

0.8 below avg 12.2

Activity Inputs

51.7 / 100

StarsRepository reach

21.2 / 30

FreshnessLast push recency

18.2 / 25

ActivityRecent commits

0.0 / 25

CommunityFork signal

12.2 / 20

Supply Chain Trust

Package Provenance

None

No package attestations found

OSSF Scorecard

3.0 / 10

OpenSSF Scorecard · scanned Aug 23, 2026

Signed Commits

83%

of last 100 commits verified

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

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?

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 49 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.

xAI Grok

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?

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

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)

2026-07-10

Scorecard Added

OSSF Scorecard: 3.8/10

2026-07-10

Grade Changed

Trust grade D → C

2026-07-10

Rank Moved

Rank rose 98 spots (#314 → #216)

2026-07-10

HVTrust Changed

HVTrust up 23.3pts (30.1 → 53.4)

2026-07-09

Newly Listed

First tracked at rank #314

GitHub → npm: grok-dev

Embed Badge Badge guide for maintainers →

For maintainers

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.3 · Raw JSON