Score breakdown
Popularity is tracked separately. Support, ads, sponsorships, and tips never affect these signals.
Why it matters
Beads addresses a practical failure mode in long-running coding work: agents lose task state and dependency context between sessions. A small, installable graph with explicit claims and blockers gives teams a shared work queue that agents can query and update without inventing a new tracking format for every repository.
Who should use it
Who should skip it
Pass on gastownhall/beads if its scope or audience does not match what your team is building right now.
About this signal
gastownhall/beads is tracked by RepoRadar as a developer tool in the Agent Infrastructure section. It was first seen on 2026-07-17 and last updated on 2026-07-17. The current verdict is 'try now' with a Gold tier and moderate setup difficulty. The standout signals for gastownhall/beads are workflow potential (9.7) and practical usefulness (9.0), while evidence quality (7.2) trails — that balance shapes where it fits best. This page summarizes the evidence RepoRadar captured from https://github.com/gastownhall/beads. The score, tier, risk label, and verdict on this page are never influenced by sponsorship, ads, or tips — they reflect only the usefulness, popularity, novelty, momentum, maturity, and evidence signals described in the RepoRadar methodology.
How this item is evaluated
RepoRadar assigned gastownhall/beads a composite score of 8.2 out of 10, placing it in the Gold tier. This score combines weighted sub-signals: usefulness (35%), novelty (18%), momentum (14%), maturity (10%), open-source/build quality (7%), evidence quality (6%), workflow potential (6%), and setup ease (4%). Popularity is tracked separately at 100.0 and never affects the composite score or tier. The risk label of 'conditional' reflects inherent user-impacting hazards, not generic novelty. Items with no risk flag may still require normal code review before production use.
Putting this into practice? Read How to vet an AI agent or MCP server before you wire it in for the checklist behind this score.
Risk explanation
The CLI writes project task state and may install agent guidance or hooks; start in a test repository and review generated files before enabling it broadly.