Research snapshot: 2026-08-21.
An inventory-to-recall workflow is a narrow, practical gap between two mature categories: household inventory and official recall search. It gives a user an ongoing stateful workflow (register, sync, match, review, resolve) instead of a one-time scanner or report generator.
A local workspace inventory covered 142 project-like directories. Local-first scanners, preflight checks, audit reports, developer tools, export verification, and evidence bundles were already heavily represented. RecallLedger deliberately avoids that repeated shape: its core value is a persistent household safety ledger with official data and human disposition state.
Targeted repository searches for recallledger, CPSC recall inventory,
product recall tracker household, and product recall watcher found no mature
direct equivalent. The intended repository name also returned GitHub 404 for
KanadeK/recallledger at the time of research.
Adjacent projects establish demand but solve different jobs:
| Project | Stars at snapshot | What it does | Deliberate distinction |
|---|---|---|---|
| grocy/grocy | 9,399 | Broad groceries and household management | RecallLedger is a small recall-focused CLI, not a home ERP. |
| sysadminsmedia/homebox | 6,971 | General home inventory and organization | RecallLedger adds official recall matching and review state rather than duplicating asset management. |
| GSA/recalls_api | 29 | Unsupported multi-agency recall API | RecallLedger is a working end-user workflow and uses the current CPSC source directly. |
| cyanheads/cpsc-recalls-mcp-server | 1 | CPSC recall search exposed over MCP | RecallLedger matches a personal inventory and persists decisions; it is not an MCP search adapter. |
Star counts are a point-in-time signal, not a promise that this repository will receive stars. Discoverability depends on continued maintenance, examples, release quality, and community fit.
CPSC documents a public REST service that returns recall data as XML or JSON:
The implementation uses the documented LastPublishDateStart filter for a
bounded first sync and idempotent incremental updates. A live research request
for 2026-08-01 onward returned 72 records and confirmed the documented JSON
shape, including RecallID, RecallNumber, LastPublishDate, Products,
ProductUPCs, Manufacturers, Hazards, and Remedies.
- CPSC data often lacks model or UPC identifiers. Brand/name similarity is therefore useful, but it is intentionally only a candidate signal.
- CPSC is the sole v0.1 source. This keeps provenance and matching semantics explainable; global or multi-agency coverage can be evaluated separately.
- A CLI and SQLite database make the first release portable and inspectable. A UI would add maintenance surface without proving the matching workflow.