Canon
All teardowns
run-llama logo

Free Verify scan · run-llama/llama_index

llama_index scores 60/100

Framework for agentic apps and document processing for AI.

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

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

Delivery controls score60
llama_index
42median 6886

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

Score

60/100

Rank 56 of 69 · median 68

Gaps

38

5 more than the median of 33

Critical

4 controls

2 root causes

Not visible

27

Needs admin access

What llama_index does wellDefault branch identifiedBranch strategy observableDefault branch protected by rulesetVisibility and ownership recordedWork arrives through a tracked path
Gaps38
llama_index
15median 3361

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

How does your team compare?

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

Docs leads the assessment.

5 of 6 visible controls pass in docs.

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

CODEOWNERS or review assignment

Covers 4 controls
  • CODEOWNERS or review assignment
  • CODEOWNERS or OWNERS file
  • Maintainer roster
  • Review of high-risk dependency changes

What Verify read

No tree evidence for owners.

Risk: With no ownership file, review lands on whoever is available rather than whoever understands the code.

text
Add CODEOWNERS.

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
  • 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
  • SBOM or dependency graphmedium
  • 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 read95 of 95All 95
Private repositoriesNoYes
ResultsPublished herePrivate to your organization

Evidence locker

Every control Verify checked

Governance

4 of 12 pass

Review

10 of 26 pass

CI & tests

19 of 30 pass

Code quality

1 of 8 pass

Security

8 of 20 pass

Agents & AI

3 of 8 pass

Release & ops

7 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 · 59Oct 16 · 60
  • Sep 29, 2026Delivery controls score 59 → 607e2c60a
  • Sep 29, 2026Concurrency cancellation · CI & tests — gap → confirmed7e2c60a

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 freeSee how your team scores

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

View run-llama/llama_index on GitHub

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