All teardowns
infiniflow logo

Free Verify scan · infiniflow/ragflow

ragflow scores 52/100

Open-source RAG engine with agent capabilities.

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

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

Delivery controls score52
ragflow
42median 6886

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

Score

52/100

Rank 64 of 69 · median 68

Gaps

45

12 more than the median of 33

Critical

6 controls

3 root causes

Not visible

26

Needs admin access

What ragflow does wellDefault branch identifiedBranch strategy observableDefault branch protected by rulesetGitHub App bypass inventoryVisibility and ownership recorded
Gaps45
ragflow
15median 3361

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

How does your team compare?

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

01

Governance leads the assessment.

5 of 5 visible controls pass in governance.

02

Code quality has the most room to improve.

7 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

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

01

Read

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

02

Judge

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

03

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 scanVerify on your repository
AccessPublicGitHub App you install
Controls read94 of 94All 94
Private repositoriesNoYes
ResultsPublished herePrivate to your organization

Evidence locker

Every control Verify checked

Review

8 of 26 pass

CI & tests

15 of 30 pass

Code quality

1 of 8 pass

Security

6 of 20 pass

Agents & AI

3 of 8 pass

Release & ops

6 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 · 55Oct 16 · 52
  • Oct 7, 2026SBOM or dependency graph · Security — needs repository admin access → confirmedcc72ecb
  • Oct 5, 2026SBOM or dependency graph · Security — confirmed → needs repository admin access2400ca8
  • Sep 30, 2026Delivery controls score 54 → 5269ff9a9
  • Sep 30, 2026Security policy · Review — confirmed → gap69ff9a9
  • Sep 30, 2026Security policy · Security — confirmed → gap69ff9a9
  • Sep 29, 2026No unattended prod migration · Release & ops — needs repository admin access → not applicable5271bb0
  • Sep 29, 2026Schema change tests · Release & ops — confirmed → not applicable5271bb0
  • Sep 29, 2026Expand/contract documented · Release & ops — confirmed → not applicable5271bb0
  • Sep 29, 2026Backup or restore note · Release & ops — gap → not applicable5271bb0
  • Sep 29, 2026Delivery controls score 55 → 545271bb0
  • Sep 29, 2026Migration tests · CI & tests — confirmed → not applicable5271bb0
  • Sep 29, 2026Migration files exist · Release & ops — confirmed → not applicable5271bb0
  • Sep 29, 2026Migrations reviewed · Release & ops — gap → not applicable5271bb0
  • Sep 23, 2026SBOM or dependency graph · Security — needs repository admin access → confirmedbc63c0c
  • Sep 22, 2026SBOM or dependency graph · Security — confirmed → needs repository admin access3a23ba0

Get this report for your own repository.

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

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

View infiniflow/ragflow on GitHub

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