Continue
Website
open-source coding agent
Is Continue safe? Thin or incomplete trust evidence. Review carefully before production use.
Compare Continue
How does it stack up against its Coding Agents neighbours?
Pick any agent to compare →In detail: Continue scores 33.2/100 (Grade D), ranked #1282 of 1371 tracked open-source AI agent projects, on evidence coverage C (2 of 5 independent signal types). The public evidence: no package-provenance attestation found; no OSSF Scorecard result yet; 79% of recent commits are signed; last pushed 2026-10-08. Every point is earned from checkable signals — never paid placement. How scoring works →
How Continue 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.
- Raise the OSSF Scorecard to 9.0no OSSF Scorecard result yet +37.1 → 70.3 B · #18 of 77
- Sign every commit79% signed today +0.6 → 33.8 D · #68 of 77
Chain of custody
Scanners check what the code says. This traces who ships Continue and whether that has changed: from the source repository, through how changes are reviewed and released, to the code you run. These are the checks for OWASP ASI04 Agentic Supply Chain Vulnerabilities.
-
Source Partly signed
github.com/continuedev/continue, Apache-2.0, last pushed 2026-10-08. 79% of the last 100 commits carry a verified signature; the rest can't be tied to a verified identity.
-
Review and release Not checked
No OpenSSF Scorecard result yet, so branch protection, code review and release signing are unverified.
-
Published packages None
Distributed as the VS Code extension continue.continue; HVTracker doesn't check marketplace source links yet.
Changes to this chain
- 2026-08-07 Provenance drift warning cleared (now: not_applicable)
Evidence behind this score
Coverage C: 2 of 5 independent evidence types found.
- GitHub repository data
- Package downloads
- Supply-chain checks (missing)
- Public actions (missing)
- Community mentions (missing)
Verify this score yourself
Every build re-issues Continue’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.
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 Continue compares in Coding Agents
- #66 RA.Aid 39.8 +6.6
- #67 GPT Pilot 39.4 +6.2
- #68 Continue 33.2 this agent
- #69 Sweep 32.5 −0.7
- #70 10x 30.3 −2.9
Bars show each HVTrust score; the tick marks Continue’s 33.2.
Where the 33.2 comes from
HVTrust dimensions vs the Coding Agents average
33.2 / 100 · 67.0% confidenceContinue Coding Agents average (77 agents)
Quick Trust Read
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 →
Rank Trend
Activity & Reach
Analysis
Activity Inputs
69.7 / 100Common questions about Continue
Does Continue publish package provenance?
Does Continue have an OpenSSF Scorecard?
Is Continue actively maintained?
What license does Continue use?
Are Continue's commits signed?
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
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 →
- browser
- code
- database
- MCP signal live
- External deps live
- Tool / plugin surface live
- Package provenance drift live
Detected changes to Continue'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.
Maintain Continue?
For maintainers
HVTrust scores Continue 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.
Reputation Timeline
Signal history
Embed Badge Badge guide for maintainers →
For maintainers
[](https://hvtracker.net/agents/continue)
<a href="https://hvtracker.net/agents/continue"><img src="https://hvtracker.net/badge/continue.svg" alt="HVTrust"></a>
Other agents in Coding Agents
GitHub REST API (repo, commits, stars, forks, license)
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.4 · Raw JSON