Is Continue safe to use?

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

What is the trust score for Continue?

Continue scores 33.0/100 on HVTracker's evidence-weighted HVTrust scale. It has 35.6k GitHub stars and is categorized under Coding Agents.

Continue

continuedev/continue

open-source coding agent

Coding Agents TypeScript Grade D Listed Apache-2.0

33.0/100

Rank #742 of 1308

Compare Continue

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 C · 2/5 signals

Last push

2026-08-24 · 1d ago

Recent change

Rank +1

Is Continue safe? Continue scores 33.0/100 (Grade D), ranked #742 of 1308 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-08-24. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in Coding Agents

#53 Devika — 36.2 (D) → #54 Tura — 36.2 (D) → #56 PearAI — 32.4 (D) → #57 zerostack — 25.9 (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-20

Rank Moved

Rank dropped 19 spots (#725 → #744)

2026-08-20

Activity Score Changed

Activity score down 8pts (77 → 70)

2026-08-16

Rank Moved

Rank dropped 15 spots (#705 → #720)

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 Continue View Coding Agents Report missing data

69.6

Activity sub-score · out of 100

#55

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

2026-08-11 2026-08-25

Activity & Reach

Stars

35.6k

Forks

5.3k

Last Push

2026-08-24

yesterday

Commits (4 wk)

Downloads (7d)

3,398,285

npm+vscode

HN mentions (30d)

—

Open Issues

475

Rank Change

was #742

Analysis

HVTrust Dimensions vs Coding Agents

33.0 / 100 · 67.0% confidence

Continue Coding Agents average (70 agents)

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

4.0 / 25

3.6 below 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

8.5 / 17

2.6 below avg 11.1

Maintenance60% last-push freshness · 40% commit activity

11.9 / 20

3.0 below avg 14.9

AdoptionLog-scaled stars · package downloads

19.6 / 20

7.3 above avg 12.3

Activity Inputs

69.6 / 100

StarsRepository reach

27.3 / 30

FreshnessLast push recency

24.9 / 25

ActivityRecent commits

0.0 / 25

CommunityFork signal

17.3 / 20

Supply Chain Trust

Package Provenance

None

No package attestations found

OSSF Scorecard

—

Not available

Signed Commits

79%

of last 100 commits verified

Is Continue safe?

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

No published build provenance is currently detected for Continue. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.

Does Continue have an OpenSSF Scorecard?

No OpenSSF Scorecard data is currently published for Continue. 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 Continue actively maintained?

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

What license does Continue use?

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

Are Continue's commits signed?

79% of the last 100 commits to Continue 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

5 detected

Public provider/service dependencies detected.

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

Tool / Plugin Surface

high confidence

Extensions

Extension based plugin/integration surface detected.

browser
code
database

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

How this surface has changed

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.

2026-08-07

Drift Warning Cleared

Provenance drift warning cleared (now: not_applicable)

2026-06-16

Tool Surface Changed

Detected tool/plugin surface changed: extension-based → marketplace

2026-06-15

Tool Surface Changed

Detected tool/plugin surface changed: marketplace → extension-based

2026-06-13

Tool Surface Changed

Detected tool/plugin surface changed: extension-based → marketplace

2026-06-11

Tool Surface Changed

Detected tool/plugin surface changed: marketplace → extension-based

2026-06-10

Tool Surface Changed

Detected tool/plugin surface changed: extension-based → marketplace

2026-06-05

Drift Warning Raised

Package-provenance drift warning: package metadata no longer clearly points at this repo

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.

Submit a correction → Add the trust badge

Reputation Timeline

Signal history

2026-08-20

Rank Moved

Rank dropped 19 spots (#725 → #744)

2026-08-20

Activity Score Changed

Activity score down 8pts (77 → 70)

2026-08-16

Rank Moved

Rank dropped 15 spots (#705 → #720)

2026-08-10

Rank Moved

Rank dropped 33 spots (#672 → #705)

2026-08-08

Rank Moved

Rank dropped 259 spots (#413 → #672)

2026-08-07

Drift Warning Cleared

Provenance drift warning cleared (now: not_applicable)

2026-07-29

Rank Moved

Rank dropped 12 spots (#401 → #413)

2026-07-21

Activity Score Changed

Activity score up 8pts (70 → 77)

2026-07-19

Activity Score Changed

Activity score down 6pts (75 → 69)

2026-07-15

Rank Moved

Rank dropped 26 spots (#370 → #396)

2026-07-15

Activity Score Changed

Activity score down 5pts (82 → 77)

2026-07-14

Rank Moved

Rank dropped 21 spots (#349 → #370)

2026-07-13

Rank Moved

Rank dropped 36 spots (#313 → #349)

2026-06-24

Rank Moved

Rank dropped 34 spots (#252 → #286)

2026-06-23

Rank Moved

Rank dropped 23 spots (#229 → #252)

2026-06-22

Rank Moved

Rank dropped 10 spots (#219 → #229)

2026-06-21

Rank Moved

Rank dropped 14 spots (#205 → #219)

2026-06-18

Rank Moved

Rank dropped 14 spots (#182 → #196)

2026-06-16

Tool Surface Changed

Detected tool/plugin surface changed: extension-based → marketplace

2026-06-16

Rank Moved

Rank rose 21 spots (#202 → #181)

2026-06-16

HVTrust Changed

HVTrust up 4.0pts (36.4 → 40.4)

2026-06-16

Activity Score Changed

Activity score up 18pts (69 → 87)

2026-06-15

Tool Surface Changed

Detected tool/plugin surface changed: marketplace → extension-based

2026-06-15

Rank Moved

Rank dropped 20 spots (#182 → #202)

2026-06-15

HVTrust Changed

HVTrust down 3.4pts (39.8 → 36.4)

2026-06-15

Activity Score Changed

Activity score down 15pts (85 → 69)

2026-06-13

Tool Surface Changed

Detected tool/plugin surface changed: extension-based → marketplace

2026-06-13

Rank Moved

Rank rose 17 spots (#201 → #184)

2026-06-13

HVTrust Changed

HVTrust up 3.3pts (36.5 → 39.8)

2026-06-13

Activity Score Changed

Activity score up 15pts (69 → 85)

2026-06-11

Tool Surface Changed

Detected tool/plugin surface changed: marketplace → extension-based

2026-06-11

Rank Moved

Rank dropped 18 spots (#183 → #201)

2026-06-11

HVTrust Changed

HVTrust down 3.3pts (39.8 → 36.5)

2026-06-11

Activity Score Changed

Activity score down 15pts (84 → 69)

2026-06-10

Tool Surface Changed

Detected tool/plugin surface changed: extension-based → marketplace

2026-06-10

HVTrust Changed

HVTrust up 3.1pts (36.7 → 39.8)

2026-06-10

Activity Score Changed

Activity score up 15pts (69 → 84)

2026-06-05

Drift Warning Raised

Package-provenance drift warning: package metadata no longer clearly points at this repo

2026-06-02

HVTrust Changed

HVTrust up 4.3pts (32.5 → 36.8)

2026-06-01

Rank Moved

Rank dropped 20 spots (#151 → #171)

2026-05-29

HVTrust Changed

HVTrust up 6.6pts (23.9 → 30.5)

GitHub → npm: continue

Embed Badge Badge guide for maintainers →

For maintainers

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

Other agents in Coding Agents

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