Is Grok Build safe to use?

Grok Build has an HVTrust score of 51.5/100 (Grade C), ranked #440 of 1283 tracked AI agent projects. This score reflects verifiable supply-chain integrity, transparency, maintenance, and adoption signals.

What is the trust score for Grok Build?

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

Grok Build

xai-org/grok-build

SpaceXAI's coding agent harness and TUI. Fullscreen, mouse interactive, extensible.

Coding Agents Rust Grade C Listed Apache-2.0

51.5/100

Rank #440 of 1283

Compare Grok Build

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-08-11 · 0d ago

Recent change

Rank +1

Is Grok Build safe? Grok Build scores 51.5/100 (Grade C), ranked #440 of 1283 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.4/10; recent commits are unsigned; last pushed 2026-08-11. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in Coding Agents

#36 Aider — 55.2 (C) → #37 Tabby — 53.1 (C) → #39 Grok CLI — 50.4 (C) → #40 HumanLayer — 49.9 (D) →

Quick Trust Read

What Would Improve It

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

Recent Changes

2026-08-10

Rank Moved

Rank dropped 17 spots (#423 → #440)

2026-08-08

Rank Moved

Rank dropped 105 spots (#315 → #420)

2026-07-19

Grade Changed

Trust grade D → C

Maintainer Checklist

Raise Scorecard signals Current OSSF Scorecard is 3.4/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.

Increase signed commits Raise the share of verified-signed commits to make maintainer identity and release history easier to trust.

Compare with another agent Get email alerts for Grok Build View Coding Agents Report missing data

86.6

Activity sub-score · out of 100

#38

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 C 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 →

Activity & Reach

Stars

24.7k

Forks

4.7k

Last Push

2026-08-11

today

Commits (4 wk)

27?

Downloads (7d)

—

HN mentions (30d)

Open Issues

Rank Change

was #440

Analysis

HVTrust Dimensions vs Coding Agents

51.5 / 100 · 100.0% confidence

Grok Build Coding Agents average (67 agents)

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

4.2 / 25

3.5 below avg 7.7

Identity / Provenance60% listing status · 40% build provenance

10.8 / 18

0.9 below avg 11.7

Transparency50% declared license · 50% OSSF Scorecard

11.4 / 17

in line with avg 11.1

Maintenance60% last-push freshness · 40% commit activity

14.9 / 20

in line with avg 15.3

AdoptionLog-scaled stars · package downloads

10.5 / 20

1.7 below avg 12.2

Activity Inputs

86.6 / 100

StarsRepository reach

26.4 / 30

FreshnessLast push recency

25.0 / 25

ActivityRecent commits

18.1 / 25

CommunityFork signal

17.1 / 20

Supply Chain Trust

Package Provenance

None

No package attestations found

OSSF Scorecard

3.4 / 10

OpenSSF Scorecard · scanned Aug 11, 2026

Signed Commits

of last 100 commits verified

Binary-Artifacts 10

Branch-Protection 5

CI-Tests -1

CII-Best-Practices 0

Code-Review 0

Contributors 0

Dangerous-Workflow -1

Dependency-Update-Tool 0

Fuzzing 10

License 10

Maintained 0

Packaging -1

Pinned-Dependencies -1

SAST 0

Security-Policy 9

Signed-Releases -1

Token-Permissions -1

Vulnerabilities 0

Is Grok Build safe?

Public trust evidence for Grok Build 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 Build publish package provenance?

No published build provenance is currently detected for Grok Build. 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 Build have an OpenSSF Scorecard?

Grok Build has an OpenSSF Scorecard score of 3.4/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 Build actively maintained?

Actively maintained. The repository was pushed to within the last 1 day(s).

What license does Grok Build use?

Grok Build ships under Apache-2.0. A declared, OSI-approved license is one of the transparency signals HVTrust scores.

Are Grok Build's commits signed?

0% of the last 100 commits to Grok Build 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

None detected

No clear third-party provider dependency detected.

Credential signal: No explicit API-key/config marker detected.

Tool / Plugin Surface

high confidence

Declared

Declared plugin/integration 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 Grok Build?

For maintainers

HVTrust scores Grok Build 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-10

Rank Moved

Rank dropped 17 spots (#423 → #440)

2026-08-08

Rank Moved

Rank dropped 105 spots (#315 → #420)

2026-07-19

Grade Changed

Trust grade D → C

2026-07-16

Rank Moved

Rank rose 12 spots (#322 → #310)

2026-07-16

Activity Score Changed

Activity score up 11pts (60 → 71)

2026-07-15

Newly Listed

First tracked at rank #322

GitHub →

Embed Badge Badge guide for maintainers →

For maintainers

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

Other agents in Coding Agents

Data sources
GitHub REST API (repo, commits, stars, forks, license) · OpenSSF Scorecard CLI · Algolia HN Search API
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.3 · Raw JSON