3 findingsStatic scanned
Runs OpenAI's Codex coding agent locally on your computer from the command line.
71.3M installs/moApache-2.0
Beads Bd
beads · Agent
Beads is an issue tracker designed for AI coding agents and used as their memory. It creates a project-local database kept under version control with Dolt, tracks dependencies between issues and finds the ones with no open blockers so an agent knows what to pick up next. You tell your agent to use it for task tracking in place of markdown to-do lists, and it then creates and updates issues as it works. This package installs the native Beads binary for Node.js environments, including Claude Code for the web.
Written by ooruby from the README of @beads/bd 1.3.1.
Not claimed by its maker. Is this yours? Prove it and answer the findings
Why it's useful
Your agent keeps its tasks, their dependencies and long-term context in a versioned project database across sessions instead of in markdown lists.
What you could do with it
- Set up Beads in a project, then tell your agent to track its tasks there instead of in markdown to-do lists.
- Ask your agent to list the ready work, meaning issues with no open blockers, and pick up the next one.
- Add a start-up hook so every Claude Code for the web session installs Beads and sets it up.
Written from its documentation: what it says it can do, not what our checks found.
Maintenance
Not measuredNo release date is on record for this package yet. The nightly publisher check records one as it reaches each npm package, about once every ten nights.
Release activity only: it says nothing about quality or safety, and a finished small package can be fine without releases. How it is measured
- Command execution is bounded
- inventory
- node child_process (scripts/postinstall.js:7)
- synchronous shell execution (scripts/postinstall.js:132)
- synchronous shell execution (scripts/postinstall.js:193)
- synchronous shell execution (scripts/postinstall.js:195)
- An inventory of where the code starts another program, not a verdict on this row: whether each one runs a fixed program or whatever it is handed takes a reading by hand.
- Data handling disclosed
- finding
- no statement of what it reads, writes or sends (README.md)
Published because it was found. A finding is information about where the limits are, not a verdict that the software is unsafe.
What this does not cover
- Everything. Treat it as you would software from anywhere else.
Receipt history: every signed receipt for every version of this listing, and what changed between them.
In its maker's words
Beads issue tracker - lightweight memory system for coding agents with native binary support
Compare with
Compare all 4How far this has been checked
Static scanned
- What it establishes
- Its published package, or for a hosted server its source repository at a recorded commit, was read file by file, without running it, by every check in our current scan.
- What it does not
- How it behaves when it runs, or anything the scan does not read yet: several rubric checks, the repository's history, and compiled code in folders named dist or build. For a hosted server, that the endpoint runs the code that was read. The ooruby Index sets out exactly what was read.
- Exactly what was read
- Version 1.3.1, the file with digest sha512-1CDk1ddWz0F76tuDvFXxklG0Ez2nt3zBMRTyDIZ40wIzulQrRPRUAiSISgHRJ/ymlMZBEnV5ZM7Q02xKZEvbFg==, as the registry publishes it. A published version cannot be replaced, so this names the same bytes for anyone who checks.
- Authentication
- Runs locally. No hosted endpoint is listed for this package. You run it on your own machine, so there is no endpoint of ours to authenticate against.
Adding it
Run it with:
npx -y @beads/bd@1.3.1Pinned to 1.3.1, which is the version the findings above were found in. Drop the version to take whatever is newest, and the report on this page stops describing what you installed.
Where this came from
- Registry
- npm
- Package
- @beads/bd
- Version read
- 1.3.1
- Resolved
- 2026-10-10
Built from source, attested
npm publishes a signed statement that this exact package was built from the repository below, at this commit. It is verifiable without taking our word for it.
- Repository
- github.com/gastownhall/beads
- Commit
- c1c4b642ac1c
- Built by
- github.com/actions/runner/github-hosted
- Registry publish attestation
- signed by npm · 2026-10-10
- Checked
- 2026-10-10
The badge, if this is your listing
It renders the current rung (static scanned) and links back here, where what that does and does not establish is one click away. It updates itself as the evidence deepens.
[](https://ooruby.com/market/beads-bd)About this listing
- Kind
- Agent
- Category
- Developer tools
- Pricing
- Free
- Sandbox
- No
- Hosted
- No
- Updated
- 2026-10-10
Similar agents
All agentsVerification records what our published tests found on a specific version at a specific date. It is not a warranty, and it does not certify that software is free of defects.