updated 2026-08-09 19:31 UTC

opencode

anomalyco/opencode

The open source coding agent.

Coding Agents TypeScript Grade D Listed MIT
45.6/100
Rank #498 of 1204
Compare opencode

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-09 · 0d ago
Recent change
Provider Added +2

Is opencode safe? opencode scores 45.6/100 (Grade D), ranked #498 of 1204 tracked open-source AI agent projects, on evidence coverage B (3 of 5 independent signal types). The public evidence: no package-provenance attestation found; no OSSF Scorecard result yet; 68% of recent commits are signed; last pushed 2026-08-09. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in Coding Agents

#41 Roo Code — 49.5 (D) → #42 Stakpak Agent — 45.9 (D) → #44 Integuru — 45.1 (D) → #45 Vibe Kanban — 45.1 (D) →

Quick Trust Read

What Would Improve It
Add or improve OSSF Scorecard coverage so safety checks are easier to verify.
Recent Changes
2026-08-09
Provider Added
Runtime surface grew — new detected provider dependencies: OpenAI, xAI Grok
2026-08-08
Rank Moved
Rank dropped 112 spots (#373 → #485)
2026-08-07
Provider Removed
Runtime surface shrank — no longer detected: xAI Grok
Maintainer Checklist
Add Scorecard coverage Expose the repository to OpenSSF Scorecard checks so supply-chain posture is easier to verify.
Publish provenance Add package provenance or release attestations so users can verify where shipped artifacts came from.
Compare with another agent Get email alerts for opencode View Coding Agents Report missing data
100.0
Activity sub-score · out of 100
#43
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-08-09 19:31 UTC · Repo last pushed today

Activity & Reach

Stars
195.4k
Forks
25.0k
Last Push
2026-08-09
today
Commits (4 wk)
466
Downloads (7d)
2,202,677
npm
HN mentions (30d)
88
Open Issues
3841
Rank Change
▼13
was #485

Analysis

HVTrust Dimensions vs Coding Agents

45.6 / 100 · 75.0% confidence

opencode Coding Agents average (65 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
3.4 / 25
4.5 below avg 7.9
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
0.9 below avg 11.7
Transparency50% declared license · 50% OSSF Scorecard
8.5 / 17
2.7 below avg 11.2
Maintenance60% last-push freshness · 40% commit activity
20.0 / 20
4.9 above avg 15.1
AdoptionLog-scaled stars · package downloads
20.0 / 20
7.7 above avg 12.3

Activity Inputs

100.0 / 100
StarsRepository reach
30 / 30
FreshnessLast push recency
25.0 / 25
ActivityRecent commits
25 / 25
CommunityFork signal
20 / 20

Supply Chain Trust

Package Provenance
None
No package attestations found
OSSF Scorecard
—
Not available
Signed Commits
68%
of last 100 commits verified

Is opencode safe?

Public trust evidence for opencode 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 opencode publish package provenance?
No published build provenance is currently detected for opencode. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.
Does opencode have an OpenSSF Scorecard?
No OpenSSF Scorecard data is currently published for opencode. 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 opencode actively maintained?
Actively maintained. The repository was pushed to within the last 1 day(s).
What license does opencode use?
opencode ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are opencode's commits signed?
68% of the last 100 commits to opencode 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
2 detected
Public provider/service dependencies detected.
Credential signal: No explicit API-key/config marker detected.
Tool / Plugin Surface
high confidence
Declared
Declared plugin/integration surface detected.
  • browser
  • code
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 opencode'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-08-09
Provider Added
Runtime surface grew — new detected provider dependencies: OpenAI, xAI Grok
2026-08-07
Provider Removed
Runtime surface shrank — no longer detected: xAI Grok
2026-07-17
Provider Added
Runtime surface grew — new detected provider dependency: xAI Grok

Maintain opencode?

For maintainers

HVTrust scores opencode 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 5Surface 2Listed 1Surface 1
2026-08-09
Provider Added
Runtime surface grew — new detected provider dependencies: OpenAI, xAI Grok
2026-08-08
Rank Moved
Rank dropped 112 spots (#373 → #485)
2026-08-07
Provider Removed
Runtime surface shrank — no longer detected: xAI Grok
2026-07-29
Rank Moved
Rank dropped 12 spots (#333 → #345)
2026-07-17
Provider Added
Runtime surface grew — new detected provider dependency: xAI Grok
2026-07-15
Rank Moved
Rank dropped 22 spots (#304 → #326)
2026-07-14
Rank Moved
Rank dropped 18 spots (#286 → #304)
2026-07-13
Rank Moved
Rank dropped 34 spots (#252 → #286)
2026-07-07
Newly Listed
First tracked at rank #248
GitHub → npm: opencode-ai

Embed Badge Badge guide for maintainers →

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

Other agents in Coding Agents

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