epic: security hardening and release readiness #10
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Goal
Before the first public release the wallet has a written threat model, a dependency policy that CI enforces, a build that someone else can reproduce, and an external review whose findings are closed or documented. This epic runs alongside the others and gates the first tagged release.
Scope
cargo-denyfor licenses and advisories;cargo-machetefor unused deps; pinned toolchain;Cargo.lockandpnpm-lock.yamlcommitted and frozen in CI.Debug; a test greps release logs for known test secrets.capabilities/*.jsonentry has a reason; no window can open arbitrary URLs.Operator-owned decisions
Definition of done
The threat model is in the repo and matches the code. CI fails on a new advisory. A release is reproduced by a second machine. The reviewer's report is linked from the release notes with every finding closed or accepted in writing.
Children: #49 (dependency policy in CI) can start as soon as #12 is green; #48 (threat model) and #50 (secret handling audit) follow #11 and #17; #51 (reproducible builds) follows #33; #52 (external review) is last and gates the first tagged release.