updated 2026-08-19 05:32 UTC

Beads

gastownhall/beads

Beads - A memory upgrade for your coding agent

Memory & Knowledge Go Grade C Listed MIT
61.3/100
Rank #316 of 1308
Compare Beads

How does it stack up against its Memory & Knowledge 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 C · 2/5 signals
Last push
2026-08-18 · 1d ago
Recent change
Rank +3

Is Beads safe? Beads scores 61.3/100 (Grade C), ranked #316 of 1308 tracked open-source AI agent projects, on evidence coverage C (2 of 5 independent signal types). The public evidence: no package-provenance attestation found; OSSF Scorecard rates its supply-chain practices 4.6/10; 43% of recent commits are signed; last pushed 2026-08-18. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in Memory & Knowledge

#24 WeKnora — 61.8 (C) → #25 MemOS — 61.8 (C) → #27 Letta — 60.4 (C) → #28 PrivateGPT — 59.7 (C) →

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 16 spots (#300 → #316)
2026-08-17
Rank Moved
Rank rose 16 spots (#317 → #301)
2026-08-13
Rank Moved
Rank dropped 18 spots (#289 → #307)
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 4.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.
Increase signed commits Raise the share of verified-signed commits to make maintainer identity and release history easier to trust.
Compare with another agent Get email alerts for Beads View Memory & Knowledge Report missing data
91.6
Activity sub-score · out of 100
#26
In Memory & Knowledge

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 C is separate — it grades how many independent signal types back the score (2 of 5), so a high score on thin evidence stays visible. Full methodology →

Signals refreshed 2026-08-19 05:32 UTC · Repo last pushed yesterday

Rank Trend

2026-08-11 2026-08-19

Activity & Reach

Stars
26.4k
Forks
1.8k
Last Push
2026-08-18
yesterday
Commits (4 wk)
794
Downloads (7d)
—
HN mentions (30d)
—
Open Issues
514
Rank Change
▼16
was #300

Analysis

HVTrust Dimensions vs Memory & Knowledge

61.3 / 100 · 100.0% confidence

Beads Memory & Knowledge average (44 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
7.9 / 25
2.0 below avg 9.9
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
1.3 below avg 12.1
Transparency50% declared license · 50% OSSF Scorecard
12.4 / 17
in line with avg 12.4
Maintenance60% last-push freshness · 40% commit activity
19.9 / 20
2.2 above avg 17.7
AdoptionLog-scaled stars · package downloads
10.6 / 20
3.0 below avg 13.6

Activity Inputs

91.6 / 100
StarsRepository reach
26.5 / 30
FreshnessLast push recency
24.9 / 25
ActivityRecent commits
25 / 25
CommunityFork signal
15.1 / 20

Supply Chain Trust

Package Provenance
None
No package attestations found
OSSF Scorecard
4.6 / 10
OpenSSF Scorecard · scanned Aug 18, 2026
Signed Commits
43%
of last 100 commits verified
Binary-Artifacts 10
Branch-Protection 3
CI-Tests 9
CII-Best-Practices 0
Code-Review 5
Contributors 10
Dangerous-Workflow 0
Dependency-Update-Tool 10
Fuzzing 0
License 10
Maintained 10
Packaging 10
Pinned-Dependencies 6
SAST 0
Security-Policy 10
Signed-Releases 0
Token-Permissions 0
Vulnerabilities 0

Is Beads safe?

Beads 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 Beads publish package provenance?
No published build provenance is currently detected for Beads. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.
Does Beads have an OpenSSF Scorecard?
Beads has an OpenSSF Scorecard score of 4.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 Beads actively maintained?
Actively maintained. The repository was pushed to within the last 1 day(s).
What license does Beads use?
Beads ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are Beads's commits signed?
43% of the last 100 commits to Beads 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
medium confidence
Declared
MCP support appears present, but direct server implementation is less certain.
Detailed evidence is not shown in the public view.
External Service Dependencies
medium confidence
1 detected
Public provider/service dependencies detected.
Credential signal: No explicit API-key/config marker detected.
Tool / Plugin Surface
high confidence
Declared
Declared plugin/integration surface detected.
Detailed evidence is not shown in the public view.
Package Provenance Drift
N/A
No package source configured
Detailed evidence is not shown in the public view.
  • MCP signal live
  • External deps live
  • Tool / plugin surface live
  • Package provenance drift live

Maintain Beads?

For maintainers

HVTrust scores Beads 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
Rank 9Listed 1
2026-08-19
Rank Moved
Rank dropped 16 spots (#300 → #316)
2026-08-17
Rank Moved
Rank rose 16 spots (#317 → #301)
2026-08-13
Rank Moved
Rank dropped 18 spots (#289 → #307)
2026-08-12
Rank Moved
Rank rose 25 spots (#314 → #289)
2026-08-10
Rank Moved
Rank dropped 19 spots (#295 → #314)
2026-08-08
Rank Moved
Rank dropped 68 spots (#227 → #295)
2026-07-25
Rank Moved
Rank dropped 10 spots (#187 → #197)
2026-07-24
Rank Moved
Rank rose 19 spots (#206 → #187)
2026-07-15
Rank Moved
Rank dropped 12 spots (#176 → #188)
2026-07-13
Newly Listed
First tracked at rank #174
GitHub →

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 61.3 Grade C
Markdown:
[![HVTrust](https://hvtracker.net/badge/beads.svg)](https://hvtracker.net/agents/beads)
HTML:
<a href="https://hvtracker.net/agents/beads"><img src="https://hvtracker.net/badge/beads.svg" alt="HVTrust"></a>

Other agents in Memory & Knowledge

Data sources
GitHub REST API (repo, commits, stars, forks, license) · OpenSSF Scorecard CLI
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.3 · Raw JSON