Security fixes are provided for the latest published release.

Use GitHub's private Security > Report a vulnerability flow for this repository. Do not open a public issue containing exploit details, household inventory, database contents, or personal identifiers.

Include the affected version, operating system, reproduction steps, impact, and the smallest safe proof of concept. Remove real inventory data before sharing.

• Inventory and review decisions remain in the user-selected SQLite file.
• The only network operation is a read-only HTTPS GET to the documented CPSC recalls endpoint with a date filter and descriptive User-Agent.
• CSV, JSON, paths, arguments, and network responses are treated as untrusted boundaries. Internal values are trusted after parsing.
• Recall URLs are displayed as data and never opened or executed.
• There are no runtime dependencies, plugins, accounts, secrets, telemetry, or remote write operations.

RecallLedger cannot guarantee recall completeness or physical-product identity. Users must verify evidence against the linked official CPSC notice.