Free Verify scan · lobehub/lobe-chat

lobe-chat scores 69/100

Agent operator/chat platform: hire, schedule, and run AI teams.

Commit eb0ddcd · 132 controls · Oct 16, 2026 · Re-checked daily

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

Delivery controls score69

lobe-chat

42median 6886

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

Score

69/100

Rank 29 of 69 · median 68

Gaps

3 more than the median of 33

Critical

7 controls

3 root causes

Not visible

Needs admin access

What lobe-chat does wellDefault branch identifiedBranch strategy observableDefault branch protected by rulesetForce-push restrictedGitHub App bypass inventory

Gaps36

lobe-chat

15median 3361

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

How does your team compare?

This is what Canon Verify found in lobe-chat'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

Docs leads the assessment.

5 of 6 visible controls pass in docs.

Security has the most room to improve.

6 visible controls remain open in security.

Priority

Fix these first

critical

Pull-request requirement on default branch

Covers 3 controls

Pull-request requirement on default branch
Required reviews
Human gate before merge

What Verify read

Required reviews: 0

Risk: Direct commits to the default branch ship unreviewed code, so no second person ever sees the change.

text

Require pull requests.

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

Open in Design

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.

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.

Overview

Control map

Public-access limit

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

No unattended prod migrationcritical
Administrator bypass restrictedhigh
Tag protectionhigh
Self-merge restrictedhigh
Bypass actors justifiedhigh
Push protection enabledhigh
Dependabot alertshigh
Secret scanning alertshigh
SAST required on default branchhigh
Environment secrets scopedhigh
Secret custodiansmedium
Agent identity in commitsmedium
Audit of agent actionsmedium
Audit of privileged actionsmedium
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	115 of 115	All 115
Private repositories	No	Yes
Results	Published here	Private to your organization

Evidence locker

Every control Verify checked

Governance

7 of 12 pass

Review

14 of 26 pass

CI & tests

24 of 30 pass

Code quality

5 of 8 pass

Security

8 of 20 pass

Agents & AI

4 of 8 pass

Release & ops

12 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 16 · 69

Oct 13, 2026Static analysis beyond lint · Code quality — gap → confirmed7243406
Oct 13, 2026Delivery controls score 67 → 697243406
Oct 13, 2026Code scanning configured · Security — gap → confirmed7243406
Oct 11, 2026OIDC instead of long-lived keys · Release & ops — confirmed → gap31b02b5
Oct 11, 2026Delivery controls score 68 → 6731b02b5
Oct 2, 2026SBOM or dependency graph · Security — needs repository admin access → confirmed1c0c1ef
Sep 30, 2026SBOM or dependency graph · Security — confirmed → needs repository admin accessbd570b2

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 lobehub/lobe-chat on GitHub

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