Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-10-19 05:19 UTC

ckumar1 / beads

Beads - A memory upgrade for your coding agent

GoMIT★ 0 stars⑂ 0 forkssince Apr 2026forkView on GitHub ↗
KindCommand-line toolMCP serverWeb interfaceLibraryhow this is determined

ckumar1/beads holds a health index of 42 out of 100, placing it in the Weak band. It scores highest on AI Readiness (96/100) and lowest on Community & Adoption (12/100). It was last updated 19 days ago. A single contributor accounts for most of its recent work.

42
overall / 100
Weak

Software health index

Metrics are grouped into weighted categories on one standardized 1–100 scale. Overall starts as their weighted mean, calibrated against the distribution of the public record so bands carry percentile meaning; when public evidence triggers the High-Risk Jurisdiction Policy, the rating is adjusted and receives an At Risk ceiling of 34.

42
Exceptional93-100The record's top tier (≈ top 5%); essentially all checked criteria met
Excellent80-92Strong across the board; minor gaps
Good65-79Healthy; gaps are limited and manageable
Moderate50-64Acceptable with notable gaps; review recommended
Weak35-49Material weaknesses across several areas
At Risk20-34Significant weaknesses; adoption warrants caution
Critical1-19Severe problems (abandoned, single-maintainer, no hygiene)
VitalityCommunity &AdoptionSustainability &GovernanceEngineeringQualitySecurityAI Readiness

Score profile

Each axis is a category. The shape matters more than the average — a healthy subject fills the whole shape, while a spike-and-crater profile means strength in one dimension is masking risk in another.

The weighted overall 45 is calibrated to 42 on the published index scale (record calibration 2026-08-02).

Ownership

Cherub KumarPersonal account
10 followers34 public repossince Sep 2013Zendesk

This repository is owned by a personal account. A single-owner project carries more continuity risk than an organization-backed one.

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publishTags
Gogithub.com/steveyegge/beadspoints to another repo — not scoredv1.3.1-13618 days ago—
npm@beads/bdpoints to another repo — not scored1.3.133,3227318 days agoissue-trackerdependency-trackingai-agentcoding-agentclaudesqlitegitproject-management
PyPIbeads-mcppoints to another repo — not scored1.3.15,69011718 days agoai-agentbeadsclaudeissue-trackermcpmodel-context-protocol

Metrics by category

Vitality

Is the project alive — is code being written and are releases shipping?

65Good · 21% of overall
How it's scored
28.8/36Push recency — last push 19 days ago
18/36Commit cadence — 26/52 weeks with commits
18/18Commit volume — 8,116 commits in the last year
0/10OpenSSF Scorecard: Maintained — 0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
Inputs used
commits_last_year8,116
human_commit_share0.86
days_since_last_push19
active_weeks_last_year26
How it's scored
16.2/27Ships releases — 100 version tags (no GitHub releases)
16.2/36Release recency — latest release 186 days ago
27/27Release cadence — a release every ~3.9 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count100
latest_release_tagv1.0.2
releases_from_tagsyes
days_since_latest_release186
mean_days_between_releases3.9
Excluded from scoring (no data or not applicable): OpenSSF Scorecard: Signed-Releases. Remaining weights renormalized.

Community & Adoption

Does the project have users, downloads, attention, and a welcoming setup for contributors?

12Critical · 17% of overall
How it's scored
0/60Stars — 0 stars
0/25Forks — 0 forks
0/15Watchers — 0 watchers
Inputs used
forks0
stars0
watchers0
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
0/22.5README
22.5/22.5License — recognized license (MIT)
0/18CONTRIBUTING guide
0/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeno
has_licenseno
readme_badges5
has_contributingno
has_issue_templateno
has_code_of_conductno
readme_badge_servicesgoreportcard.com, shields.io
has_pull_request_templateno

Sustainability & Governance

Will the project survive its people — bus factor, responsiveness, who backs it, and package upkeep?

30At Risk · 23% of overall
How it's scored
9/54Bus factor — 1 contributor(s) cover half of all commits
5.7/22.5Commit distribution — top contributor authored 75% of commits
13.5/13.5Contributor breadth — 98 contributors
10/10OpenSSF Scorecard: Contributors — project has 28 contributing companies or organizations
Inputs used
bus_factor1
contributors_sampled98
top_contributor_share0.746
How it's scored
0/42Issue resolution — no issues or no data
0/30PR acceptance — no decided pull requests or no data
0/13Newcomer PR acceptance — no first-time contributor's PR decided in 30d
0/15OpenSSF Scorecard: Code-Review — Found 0/30 approved changesets -- score normalized to 0
Inputs used
merged_prs0
open_issues0
closed_issues0
prs_merged_7d0
prs_decided_7d0
prs_merged_30d0
prs_decided_30d0
issue_closed_ratio—
closed_unmerged_prs0
first_time_authors_30d0
first_time_prs_merged_30d0
first_time_prs_decided_30d0
Excluded from scoring (no data or not applicable): Issue resolution, PR acceptance, Newcomer PR acceptance. Remaining weights renormalized.
How it's scored
10/30Ownership backing — personal (user) account
0/20Verified domain — not applicable to user accounts
7.5/25Owner reach — 10 followers of ckumar1
23.2/25Track record — 34 public repos, account ~13 yr old
Inputs used
followers10
owner_typeUser
is_verified—
owner_loginckumar1
public_repos34
account_age_days4,783
Excluded from scoring (no data or not applicable): Verified domain. Remaining weights renormalized.

Engineering Quality

Are baseline engineering and documentation practices in place?

65Good · 19% of overall
How it's scored
24/24CI workflows — 9 workflow(s)
24/24Tests present
16/16Linter config — .golangci.yml, integrations/beads-mcp/pyproject.toml ([tool.ruff])
9.6/9.6Pre-commit hooks
0/6.4.editorconfig
0/20OpenSSF Scorecard: CI-Tests — no data
Inputs used
has_ciyes
has_testsyes
has_editorconfigno
has_linter_configyes
has_precommit_configyes
Excluded from scoring (no data or not applicable): OpenSSF Scorecard: CI-Tests. Remaining weights renormalized.

Documentation

25At Risk
How it's scored
0/30README
25/25Documentation directory
0/15Documentation / homepage site
0/10Repository description
0/10Topics
0/10Wiki
Inputs used
topics—
has_wikino
homepage—
docs_site—
has_readmeno
has_docs_diryes
has_descriptionno

Security

Are visible security and supply-chain practices strong, without unresolved high-risk jurisdiction exposure?

39Weak · 16% of overall
How it's scored
7.5/7.5Binary-Artifacts — no binaries found in the repo
0/7.5Branch-Protection — branch protection not enabled on development/release branches
0/2.5CI-Tests — no data
0/2.5CII-Best-Practices — no effort to earn an OpenSSF best practices badge detected
0/7.5Code-Review — Found 0/30 approved changesets -- score normalized to 0
2.5/2.5Contributors — project has 28 contributing companies or organizations
10/10Dangerous-Workflow — no dangerous workflow patterns detected
7.5/7.5Dependency-Update-Tool — update tool detected
0/5Fuzzing — project is not fuzzed
2.5/2.5License — license file detected
0/7.5Maintained — 0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
0/5Packaging — no data
0/5Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 0
0/5SAST — no SAST tool detected
5/5Security-Policy — security policy file detected
0/7.5Signed-Releases — no data
0/7.5Token-Permissions — detected GitHub workflow tokens with excessive permissions
0/7.5Vulnerabilities — 234 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated15
scorecard_versionv5.5.0
checks_inconclusive3
scorecard_aggregate3.9
Excluded from scoring (no data or not applicable): CI-Tests, Packaging, Signed-Releases. Remaining weights renormalized.

AI Readiness

How well is the repo equipped to be developed and maintained with AI coding agents? Carries a deliberately small weight (4%): agent tooling is a real maintenance signal, but a repository with none can still reach 100/100.

96Exceptional · 4% of overall
How it's scored
45/45Agent instructions — .github/copilot-instructions.md, AGENTS.md, CLAUDE.md, claude-plugin/skills/beads/CLAUDE.md, claude-plugin/skills/beads/resources/AGENTS.md, cmd/bd/AGENTS.md, docs/CLAUDE.md
15/15Machine-readable docs (llms.txt) — llms.txt present
40/40Legible commit history — 77 of 86 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtyes
llms_txt_url—
legible_history_share0.895
agent_instruction_files.github/copilot-instructions.md, AGENTS.md, CLAUDE.md, claude-plugin/skills/beads/CLAUDE.md, claude-plugin/skills/beads/resources/AGENTS.md, cmd/bd/AGENTS.md, docs/CLAUDE.md
agent_instruction_max_bytes9,639
How it's scored
18/18One-command bootstrap — Makefile
22/22Automated tests
11/11Lint / format config — .golangci.yml, integrations/beads-mcp/pyproject.toml ([tool.ruff])
11/11Static type checking — integrations/beads-mcp/src/beads_mcp/py.typed, website/tsconfig.json
10/10Reproducible environment — devcontainer, Nix, lockfile
10/10Demonstrated agent practice — 23 of the last 100 commits agent-authored or agent-credited
8/8Automated maintenance — 14 of the last 100 commits are automated dependency updates
0/10OpenSSF Scorecard: Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 0
Inputs used
has_nixyes
has_testsyes
lockfilesgo.sum, package-lock.json, uv.lock
has_dockerfileno
typed_languageyes
bootstrap_filesMakefile
has_devcontaineryes
has_linter_configyes
typecheck_configsintegrations/beads-mcp/src/beads_mcp/py.typed, website/tsconfig.json
agent_commit_share0.23
toolchain_manifestsexamples/bd-example-extension-go/go.mod, examples/library-usage/go.mod, go.mod
dependency_bot_commit_share0.14
How it's scored
45/45Type-checkable code — Go (statically typed)
54.4/55Manageable file sizes — 11/1,088 source files over 60KB
Inputs used
primary_languageGo
largest_source_bytes109,152
source_files_sampled1,088
oversized_source_files11
How it's scored
0/40API schema (OpenAPI/GraphQL/proto) — not applicable to this kind of software
20/20MCP server
40/40Runnable examples — examples, recipes
Inputs used
example_dirsexamples, recipes
has_mcp_signalyes
api_schema_files—
interfaces_expected_of—
Excluded from scoring (no data or not applicable): API schema (OpenAPI/GraphQL/proto). Remaining weights renormalized.

Key facts

0GitHub stars
98contributors
8,116commits, last 12 months
19days since last push
100releases
1bus factor
0open issues
Go, npmpackage ecosystems

Data collection warnings

  • Community profile unavailable
  • go package 'github.com/steveyegge/beads' points at a different repository (https://github.com/steveyegge/beads); excluded from ecosystem scoring
  • npm package '@beads/bd' points at a different repository (https://github.com/gastownhall/beads); excluded from ecosystem scoring
  • pypi package 'beads-mcp' points at a different repository (https://github.com/gastownhall/beads); excluded from ecosystem scoring
  • GitHub dependency-graph SBOM unavailable (404); the dependency graph may be disabled for this repository

More detail

OpenSSF Scorecard 3.9 / 10
3.9aggregate

Independent, tool-agnostic security assessment from the open-source OpenSSF Scorecard. Each check rewards a security practice, not a specific vendor's tool. Checks Scorecard could not determine are marked n/a and excluded from the security score (never counted as zero).Scorecard v5.5.0 · 2026-10-19 05:19 UTC

10Binary-Artifactsno binaries found in the repo
0Branch-Protectionbranch protection not enabled on development/release branches
n/aCI-Testsno pull request found
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
0Code-ReviewFound 0/30 approved changesets -- score normalized to 0
10Contributorsproject has 28 contributing companies or organizations
10Dangerous-Workflowno dangerous workflow patterns detected
10Dependency-Update-Toolupdate tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
0Maintained0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
n/aPackaginginternal error: Client.Actions.ListWorkflowRunsByFileName: internal error: ListWorkflowRunsByFileName: GET https://api.github.com/repos/ckumar1/beads/actions/workflows/release.yml/runs?status=success: 404 Not Found []
0Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
0SASTno SAST tool detected
10Security-Policysecurity policy file detected
n/aSigned-Releasesno releases found
0Token-Permissionsdetected GitHub workflow tokens with excessive permissions
0Vulnerabilities234 existing vulnerabilities detected
Direct dependencies 43
RegistryPackageVersion constraintManifest
Gocharm.land/glamour/v2v2.0.0go.mod
Gocharm.land/huh/v2v2.0.3go.mod
Gocharm.land/lipgloss/v2v2.0.3go.mod
Gogithub.com/BurntSushi/tomlv1.6.0go.mod
Gogithub.com/JohannesKaufmann/html-to-markdown/v2v2.5.0go.mod
Gogithub.com/anthropics/anthropic-sdk-gov1.37.0go.mod
Gogithub.com/cenkalti/backoff/v4v4.3.0go.mod
Gogithub.com/dolthub/driverv1.84.1go.mod
Gogithub.com/go-sql-driver/mysqlv1.9.3go.mod
Gogithub.com/olebedev/whenv1.1.0go.mod
Gogithub.com/spf13/cobrav1.10.2go.mod
Gogithub.com/spf13/viperv1.21.0go.mod
Gogithub.com/stretchr/testifyv1.11.1go.mod
Gogithub.com/testcontainers/testcontainers-gov0.42.0go.mod
Gogithub.com/testcontainers/testcontainers-go/modules/doltv0.42.0go.mod
Gogo.opentelemetry.io/otelv1.43.0go.mod
Gogo.opentelemetry.io/otel/exporters/otlp/otlpmetric/otlpmetrichttpv1.43.0go.mod
Gogo.opentelemetry.io/otel/exporters/stdout/stdoutmetricv1.43.0go.mod
Gogo.opentelemetry.io/otel/exporters/stdout/stdouttracev1.43.0go.mod
Gogo.opentelemetry.io/otel/metricv1.43.0go.mod
Gogo.opentelemetry.io/otel/sdkv1.43.0go.mod
Gogo.opentelemetry.io/otel/sdk/metricv1.43.0go.mod
Gogo.opentelemetry.io/otel/tracev1.43.0go.mod
Gogolang.org/x/syncv0.20.0go.mod
Gogolang.org/x/sysv0.43.0go.mod
Gogolang.org/x/termv0.42.0go.mod
Gogopkg.in/yaml.v3v3.0.1go.mod
Gorsc.io/scriptv0.0.2go.mod
Gogithub.com/google/uuidv1.6.0go.mod
Gogithub.com/microcosm-cc/bluemondayv1.0.27go.mod
Gogithub.com/subosito/gotenvv1.6.0go.mod
Gogithub.com/yuin/goldmarkv1.8.2go.mod
npm@docusaurus/core3.9.2website/package.json
npm@docusaurus/preset-classic3.9.2website/package.json
npm@docusaurus/theme-mermaid^3.9.2website/package.json
npm@mdx-js/react^3.0.0website/package.json
npmclsx^2.0.0website/package.json
npmprism-react-renderer^2.3.0website/package.json
npmreact^19.0.0website/package.json
npmreact-dom^19.0.0website/package.json
PyPIfastmcp==3.2.4integrations/beads-mcp/pyproject.toml
PyPIpydantic==2.13.2integrations/beads-mcp/pyproject.toml
PyPIpydantic-settings==2.13.1integrations/beads-mcp/pyproject.toml
All dependencies not collected

The resolved dependency set could not be collected for this report: GitHub dependency-graph SBOM unavailable (404); the dependency graph may be disabled for this repository

Raw JSON report machine-readable

Feedback

Spotted something off in this report, or have thoughts to share? Wrong measurements, missed tooling, ideas, questions — anything is welcome. Every message is read and gets a response.

The message is kept through sign-in.

Scores are signals, not warranties. They reflect publicly visible practices on GitHub — not a code audit, and not a security guarantee.

Missing data is excluded and weights renormalized, never scored as zero. Methodology is versioned and open: metrics v2.10.0, schema v0.34.0 — full methodology · metrics wiki.

How one result sits in the wider record: aggregate statistics — Go, npm, PyPI.