Burr has an HVTrust score of 67.4/100 (Grade B), ranked #418 of 1371 tracked AI agent projects. This score reflects verifiable supply-chain integrity, transparency, maintenance, and adoption signals.

What is the trust score for Burr?

Burr scores 67.4/100 on HVTracker's evidence-weighted HVTrust scale. It has 2.6k GitHub stars and is categorized under Agent Frameworks.

Burr

Repository Website by apache

Build applications that make decisions (chatbots, agents, simulations, etc...). Monitor, trace, persist, and execute on your own infrastructure.

Agent Frameworks Python Listed Apache-2.0

Is Burr safe? Promising trust profile, but some evidence still deserves review.

OSSF Scorecard 6.5 / 10

Provenance None

Signed commits 92%

Last push yesterday

Advisories None known

Compare Burr

How does it stack up against its Agent Frameworks neighbours?

Pick any agent to compare →

Suggest a correction

In detail: Burr scores 67.4/100 (Grade B), ranked #418 of 1371 tracked open-source AI agent projects, on evidence coverage A (4 of 5 independent signal types). The public evidence: no package-provenance attestation found; OSSF Scorecard rates its supply-chain practices 6.5/10; 92% of recent commits are signed; no published advisory affects its latest release (burr); last pushed 2026-10-08. Every point is earned from checkable signals — never paid placement. How scoring works →

How Burr could raise its score

Each line changes one public signal and recomputes with the live scoring function. The gains don't add up exactly, because the score is capped near the top.

Publish build provenance for its packagesPyPI Trusted Publishing attestations +14.4 → 81.8 A · #14 of 129
Raise the OSSF Scorecard from 6.5 to 9.0lowest checks: CII-Best-Practices 0, Fuzzing 0, Pinned-Dependencies 0 +5.2 → 72.6 B · #19 of 129

Already done? Suggest a correction Add the trust badge

Chain of custody

Scanners check what the code says. This traces who ships Burr and whether that has changed: from the source repository, through how changes are reviewed and released, to the package you install. These are the checks for OWASP ASI04 Agentic Supply Chain Vulnerabilities.

Source Signed

github.com/apache/burr, Apache-2.0, last pushed 2026-10-08. 92% of the last 100 commits carry a verified signature, so changes trace to a verified account.
Review and release Mixed

OpenSSF Scorecard rates the repository's practices 6.5/10 (scanned Oct 6, 2026). The checks that decide who can get a change released:
- Code Review10
- Branch Protection8
- Signed Releases8
- Dangerous Workflow10
- Token Permissions0
- Pinned Dependencies0
All 18 Scorecard checks

Binary-Artifacts 10

Branch-Protection 8

CI-Tests 10

CII-Best-Practices 0

Code-Review 10

Contributors 10

Dangerous-Workflow 10

Dependency-Update-Tool 10

Fuzzing 0

License 10

Maintained 10

Packaging -1

Pinned-Dependencies 0

SAST 0

Security-Policy 10

Signed-Releases 8

Token-Permissions 0

Vulnerabilities 0
Published packages Linked, not attested
- PyPI burr Source link points back to this repo No build attestation
Without a build attestation, nothing proves the published files were built from this repository.
What you install today No known advisories

Latest release checked: burr 0.42.0. No published advisory affects it (OSV, checked 2026-10-09).

Changes to this chain

2026-10-02 Provenance drift warning cleared (now: unknown)
2026-08-07 Package-provenance drift warning: package metadata no longer clearly points at this repo

Evidence behind this score

Coverage A: 4 of 5 independent evidence types found.

GitHub repository data
Package downloads
Supply-chain checks
Public actions (missing)
Community mentions

Verify this score yourself

Every build re-issues Burr’s score as an Ed25519-signed credential, valid for 7 days. You can check it offline against HVTracker’s published key; if anyone changes a number after signing, verification fails.

Signed credential (JSON) How to verify

What this score doesn’t check

It covers who ships the code, not what the code does. It doesn’t read tool descriptions or prompts for injected instructions, watch runtime behaviour, or find bugs nobody has disclosed yet. For that, run a content scanner before you connect it, such as Cisco MCP Scanner or Snyk Agent Scan.

How Burr compares in Agent Frameworks

Bars show each HVTrust score; the tick marks Burr’s 67.4.

Where the 67.4 comes from

HVTrust dimensions vs the Agent Frameworks average

67.4 / 100 · 100.0% confidence

Burr Agent Frameworks average (129 agents)

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

12.7 / 25

3.1 above avg 9.6

Identity / Provenance60% listing status · 40% build provenance

10.8 / 18

0.8 below avg 11.6

Transparency50% declared license · 50% OSSF Scorecard

14.0 / 17

1.7 above avg 12.3

Maintenance60% last-push freshness · 40% commit activity

16.6 / 20

2.3 above avg 14.3

AdoptionLog-scaled stars · package downloads

12.9 / 20

1.7 above avg 11.2

Quick Trust Read

What Would Improve It

Publish package provenance or release attestations for stronger supply-chain evidence.

Recent Changes

2026-10-09

Rank Moved

Rank dropped 12 spots (#406 → #418)

2026-10-03

Grade Changed

Trust grade C → B

2026-10-03

Rank Moved

Rank rose 138 spots (#543 → #405)

Maintainer Checklist

Raise Scorecard signals Current OSSF Scorecard is 6.5/10. Tighten the weakest checks to improve public safety evidence.

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 Burr View Agent Frameworks Report missing data

70.8

Activity sub-score · out of 100

#31

In Agent Frameworks

How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption. Grade B reflects the trust score band: A ≥ 80, B ≥ 65, C ≥ 50, D < 50. Evidence coverage A is separate — it grades how many independent signal types back the score (4 of 5), so a high score on thin evidence stays visible. Full methodology →

Rank Trend

2026-09-29 2026-10-09

Activity & Reach

Stars

2.6k

Forks

203

Last Push

2026-10-08

yesterday

Commits (4 wk)

Downloads (7d)

3,592

pypi

HN mentions (30d)

Open Issues

Rank Change

▼12

was #406

Analysis

Activity Inputs

70.8 / 100

StarsRepository reach

20.5 / 30

FreshnessLast push recency

24.9 / 25

ActivityRecent commits

14.7 / 25

CommunityFork signal

10.7 / 20

Common questions about Burr

Burr has a mixed signal profile. Some trust indicators are present, others are missing. Whether it is safe for your use case depends on which gaps matter to you — review the breakdown below before adopting in production.

Does Burr publish package provenance?

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

Does Burr have an OpenSSF Scorecard?

Burr has an OpenSSF Scorecard score of 6.5/10. The Scorecard checks for branch protection, signed releases, dependency updates, fuzzing, code review, and other supply-chain hygiene items. See the full check breakdown on this page.

Is Burr actively maintained?

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

What license does Burr use?

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

Are Burr's commits signed?

92% of the last 100 commits to Burr 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

None detected

No MCP server signal detected.

Detailed evidence is not shown in the public view.

External Service Dependencies

high confidence

5 detected

Public provider/service dependencies detected.

Credential signal: API keys or service config markers documented.

Tool / Plugin Surface

high confidence

2 tags

Broad capability areas detected.

database
search

Detailed evidence is not shown in the public view.

Package Provenance Drift

high confidence

Match

Published package metadata matches the tracked repo

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 Burr'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-10-02

Drift Warning Cleared

Provenance drift warning cleared (now: unknown)

2026-08-07

Drift Warning Raised

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

Maintain Burr?

For maintainers

HVTrust scores Burr 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-10-09

Rank Moved

Rank dropped 12 spots (#406 → #418)

2026-10-03

Grade Changed

Trust grade C → B

2026-10-03

Rank Moved

Rank rose 138 spots (#543 → #405)

2026-10-03

HVTrust Changed

HVTrust up 3.9pts (63.4 → 67.3)

2026-10-02

Drift Warning Cleared

Provenance drift warning cleared (now: unknown)

2026-10-02

Rank Moved

Rank rose 139 spots (#682 → #543)

2026-10-02

HVTrust Changed

HVTrust up 4.9pts (58.5 → 63.4)

2026-09-28

Rank Moved

Rank dropped 23 spots (#663 → #686)

2026-09-23

Rank Moved

Rank dropped 397 spots (#251 → #648)

2026-09-21

Rank Moved

Rank rose 381 spots (#632 → #251)

2026-09-11

Rank Moved

Rank rose 10 spots (#637 → #627)

2026-09-09

Rank Moved

Rank dropped 11 spots (#632 → #643)

2026-09-07

Rank Moved

Rank dropped 36 spots (#588 → #624)

2026-09-06

Rank Moved

Rank dropped 11 spots (#577 → #588)

2026-09-05

Rank Moved

Rank dropped 80 spots (#497 → #577)

2026-09-04

Rank Moved

Rank dropped 33 spots (#464 → #497)

2026-09-03

Rank Moved

Rank dropped 19 spots (#445 → #464)

2026-09-02

Rank Moved

Rank rose 17 spots (#462 → #445)

2026-08-31

Rank Moved

Rank dropped 34 spots (#420 → #454)

2026-08-30

Rank Moved

Rank rose 12 spots (#432 → #420)

2026-08-27

Rank Moved

Rank dropped 11 spots (#421 → #432)

2026-08-26

Rank Moved

Rank dropped 43 spots (#378 → #421)

2026-08-25

Rank Moved

Rank dropped 19 spots (#359 → #378)

2026-08-24

Rank Moved

Rank dropped 16 spots (#343 → #359)

2026-08-22

Rank Moved

Rank rose 16 spots (#356 → #340)

2026-08-19

Rank Moved

Rank dropped 16 spots (#343 → #359)

2026-08-17

Rank Moved

Rank rose 17 spots (#362 → #345)

2026-08-13

Rank Moved

Rank dropped 12 spots (#346 → #358)

2026-08-12

Rank Moved

Rank rose 12 spots (#358 → #346)

2026-08-10

Rank Moved

Rank dropped 19 spots (#338 → #357)

2026-08-08

Rank Moved

Rank dropped 87 spots (#254 → #341)

2026-08-07

Drift Warning Raised

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

2026-07-26

Rank Moved

Rank rose 14 spots (#149 → #135)

2026-07-24

Grade Changed

Trust grade C → B

2026-07-15

Rank Moved

Rank dropped 11 spots (#151 → #162)

2026-07-13

Rank Moved

Rank dropped 17 spots (#125 → #142)

GitHub → Website → PyPI: burr

Embed Badge Badge guide for maintainers →

For maintainers

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

Other agents in Agent Frameworks

Data sources
GitHub REST API (repo, commits, stars, forks, license) · PyPI / pypistats (downloads, provenance) · OpenSSF Scorecard CLI · Algolia HN Search API
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.4 · Raw JSON

Burr

How Burr could raise its score

Chain of custody

Source Signed

Review and release Mixed

Published packages Linked, not attested

What you install today No known advisories

Changes to this chain

Evidence behind this score

Verify this score yourself

What this score doesn’t check

How Burr compares in Agent Frameworks

Where the 67.4 comes from

HVTrust dimensions vs the Agent Frameworks average

Quick Trust Read

Rank Trend

Activity & Reach

Analysis

Activity Inputs

Common questions about Burr

AI agent surface

Maintain Burr?

Reputation Timeline

Embed Badge Badge guide for maintainers →

Other agents in Agent Frameworks