Free Verify scan · continuedev/continue

continue scores 68/100

Open-source AI coding agents for the IDE, terminal, and CI.

Commit 5522c6f · 132 controls · Oct 15, 2026 · Re-checked daily

Scanned with public access only. Customer results are never published.

Delivery controls score68

continue

42median 6886

Out of 100. Stronger than 43% of the 68 other assessed repositories.

Score

68/100

Rank 33 of 69 · median 68

Gaps

3 fewer than the median of 33

Critical

6 controls

3 root causes

Not visible

Needs admin access

What continue does wellDefault branch identifiedBranch strategy observableDefault branch protected by rulesetGitHub App bypass inventoryVisibility and ownership recorded

Gaps30

continue

15median 3361

Visible controls Verify found unmet. Fewer is better. Stronger than 65% of the 68 other assessed repositories.

How does your team compare?

This is what Canon Verify found in continue's public configuration. Your team's process probably has the same gaps. Most private repos do.

See how your team scores

5 minutes. No repository access needed.

Scan your own repo with Verify (free)

Analysis

Our read

Governance leads the assessment.

5 of 5 visible controls pass in governance.

Code quality has the most room to improve.

6 visible controls remain open in code quality.

Priority

Fix these first

critical

Production approvers named

Covers 3 controls

Production approvers named
Production protection
Production reviewers resolved

What Verify read

No resolved production reviewers.

Risk: Unnamed production approvers mean deployment approval falls to whoever is nearby when the button needs pressing.

text

Name production reviewers.

Have this gap too? Start from the PR Review Pipeline flow.

Open in Design

critical

Required checks match workflow names

Covers 4 controls

Required checks match workflow names
Required status checks strict
Required check includes tests
Required lint check

What Verify read

Required checks: none

Risk: If required checks do not match the jobs that run, a rule appears to protect the branch while enforcing nothing.

text

Align required checks with jobs.

critical

Unit test command

Covers 2 controls

Unit test command
Tests run in CI

What Verify read

No tree evidence for test.

Risk: With no test command, there is no repeatable way to establish whether the code still works.

text

Add a test script.

Overview

Control map

Public-access limit

27 controls this scan couldn't read

This free scan used public access only. These controls live in settings only a repository admin can read. Verify checks them on your connected repository.

Pull-request requirement on default branchcritical
Required reviewscritical
Human gate before mergecritical
Force-push restrictedhigh
Administrator bypass restrictedhigh
Tag protectionhigh
CODEOWNERS reviews requiredhigh
Stale reviews dismissedhigh
Last-push approval requiredhigh
Self-merge restrictedhigh
Bypass actors justifiedhigh
Push protection enabledhigh
Dependabot alertshigh
Secret scanning alertshigh
SAST required on default branchhigh
Environment secrets scopedhigh
Signed commits requiredmedium
Branch deletion protectedmedium
Conversation resolution requiredmedium
Merge queue or serialized mergemedium
Secret custodiansmedium
Agent identity in commitsmedium
Audit of agent actionsmedium
Audit of privileged actionsmedium
Linear history or documented merge methodlow
Private vulnerability reportinglow
Wait timer or freeze windowlow

Get Verify

Method

How Verify works

Read

Verify reads the repository at a pinned commit: settings, rulesets, workflows, and files.

Judge

Each control is checked against a written expectation. Same inspector, same criteria, every repository.

Prove

Every result shows the evidence Verify read. Assessments re-run daily, and changes are logged.

132 controls · 69 repositories assessed · re-run daily

	This free scan	Verify on your repository
Access	Public	GitHub App you install
Controls read	95 of 95	All 95
Private repositories	No	Yes
Results	Published here	Private to your organization

Evidence locker

Every control Verify checked

Review

15 of 26 pass

CI & tests

17 of 30 pass

Code quality

2 of 8 pass

Security

8 of 20 pass

Agents & AI

4 of 8 pass

Release & ops

9 of 22 pass

Docs

5 of 6 pass

Assessment timeline

Canon re-assesses this repository daily. An entry appears only when something changed — the score, a control's outcome, or a control ceasing to apply.

Sep 21 · 68Oct 15 · 68

Oct 3, 2026SBOM or dependency graph · Security — needs repository admin access → confirmed5522c6f
Oct 1, 2026SBOM or dependency graph · Security — confirmed → needs repository admin access5522c6f
Sep 26, 2026SBOM or dependency graph · Security — needs repository admin access → confirmed5522c6f
Sep 24, 2026SBOM or dependency graph · Security — confirmed → needs repository admin access5522c6f

Get this report for your own repository.

Canon Verify runs the same inspection on your private repo. Read-only GitHub App. First scan free.

Scan your repo free See how your team scores

Read-only access. No code stored. How Canon handles your data →

View continuedev/continue on GitHub

Maintain continue? If anything here is inaccurate or out of date, email security@strikelabs.co and we'll correct it.