Burr

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

Agent Frameworks Python Grade C Listed Apache-2.0
58.6/100
Rank #358 of 1308
Compare Burr

How does it stack up against its Agent Frameworks neighbours?

Pick any agent to compare →

Promising trust profile, but some evidence still deserves review.

Open compare tool Suggest correction
Listing state
Listed
Evidence coverage
Grade A · 4/5 signals
Last push
2026-08-17 · 2d ago
Recent change
Rank +3

Is Burr safe? Burr scores 58.6/100 (Grade C), ranked #358 of 1308 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.6/10; 60% of recent commits are signed; last pushed 2026-08-17. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in Agent Frameworks

Quick Trust Read

What Would Improve It
Publish package provenance or release attestations for stronger supply-chain evidence.
Recent Changes
2026-08-19
Rank Moved
Rank dropped 15 spots (#343 → #358)
2026-08-17
Rank Moved
Rank rose 17 spots (#362 → #345)
2026-08-13
Rank Moved
Rank dropped 12 spots (#346 → #358)
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 6.6/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.
74.6
Activity sub-score · out of 100
#49

How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption. Grade C 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 →

Signals refreshed 2026-08-19 05:32 UTC · Repo last pushed 2 days ago

Rank Trend

2026-08-11 2026-08-19

Activity & Reach

Stars
2.5k
Forks
184
Last Push
2026-08-17
2 days ago
Commits (4 wk)
31
Downloads (7d)
5,522
pypi
HN mentions (30d)
0
Open Issues
51
Rank Change
▼15
was #343

Analysis

HVTrust Dimensions vs Agent Frameworks

58.6 / 100 · 100.0% confidence

Burr Agent Frameworks average (119 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
11.2 / 25
3.1 above avg 8.1
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
0.8 below avg 11.6
Transparency50% declared license · 50% OSSF Scorecard
14.1 / 17
2.6 above avg 11.5
Maintenance60% last-push freshness · 40% commit activity
17.9 / 20
3.5 above avg 14.4
AdoptionLog-scaled stars · package downloads
13.2 / 20
1.9 above avg 11.3

Activity Inputs

74.6 / 100
StarsRepository reach
20.4 / 30
FreshnessLast push recency
24.7 / 25
ActivityRecent commits
18.8 / 25
CommunityFork signal
10.5 / 20

Supply Chain Trust

Package Provenance
None
No package attestations found
OSSF Scorecard
6.6 / 10
OpenSSF Scorecard · scanned Aug 17, 2026
Signed Commits
60%
of last 100 commits verified
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 2

Is Burr safe?

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.6/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 2 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?
60% 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
Warning
1 package source mismatch detected
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-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.

Reputation Timeline

Signal history
Rank 16Grade 11HVTrust 8Scorecard 4Scorecard 3Listed 1Score 1Drift 1
2026-08-19
Rank Moved
Rank dropped 15 spots (#343 → #358)
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)
2026-07-11
Rank Moved
Rank rose 13 spots (#140 → #127)
2026-07-02
Grade Changed
Trust grade B → C
2026-06-20
Grade Changed
Trust grade C → B
2026-06-18
Scorecard Added
OSSF Scorecard: 6.5/10
2026-06-18
Grade Changed
Trust grade D → C
2026-06-18
Rank Moved
Rank rose 75 spots (#190 → #115)
2026-06-18
HVTrust Changed
HVTrust up 26.3pts (38.5 → 64.8)
2026-06-16
Scorecard Removed
OSSF Scorecard no longer detected
2026-06-16
Grade Changed
Trust grade C → D
2026-06-16
Rank Moved
Rank dropped 77 spots (#111 → #188)
2026-06-16
HVTrust Changed
HVTrust down 26.0pts (64.5 → 38.5)
2026-06-15
Scorecard Added
OSSF Scorecard: 6.4/10
2026-06-15
Grade Changed
Trust grade D → C
2026-06-15
Rank Moved
Rank rose 76 spots (#187 → #111)
2026-06-15
HVTrust Changed
HVTrust up 25.9pts (38.6 → 64.5)
2026-06-13
Scorecard Removed
OSSF Scorecard no longer detected
2026-06-13
Grade Changed
Trust grade C → D
2026-06-13
Rank Moved
Rank dropped 77 spots (#111 → #188)
2026-06-13
HVTrust Changed
HVTrust down 26.1pts (64.7 → 38.6)
2026-06-11
Scorecard Added
OSSF Scorecard: 6.4/10
2026-06-11
Grade Changed
Trust grade D → C
2026-06-11
Rank Moved
Rank rose 77 spots (#188 → #111)
2026-06-11
HVTrust Changed
HVTrust up 26.3pts (38.4 → 64.7)
2026-06-10
Scorecard Removed
OSSF Scorecard no longer detected
2026-06-10
Grade Changed
Trust grade C → D
2026-06-10
Rank Moved
Rank dropped 87 spots (#101 → #188)
2026-06-10
HVTrust Changed
HVTrust down 26.5pts (64.9 → 38.4)
2026-06-07
Grade Changed
Trust grade B → C
2026-05-29
HVTrust Changed
HVTrust up 9.9pts (54.5 → 64.4)
2026-05-28
Activity Score Changed
Activity score up 15pts (54 → 69)
2026-05-27
Scorecard Added
OSSF Scorecard: 6.4/10
2026-05-27
Grade Changed
Trust grade C → B
2026-05-27
HVTrust Changed
HVTrust up 16.8pts (40.2 → 57.0)
2026-05-25
Newly Listed
First tracked at rank #128

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 58.6 Grade C
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.3 · Raw JSON