feat: map Wallet Security onto the Security Map - #635
Merged
mattaereal merged 1 commit intoSep 14, 2026
Merged
Conversation
Add a coverage work queue that lists unmitigated threats, undocumented controls, empty frameworks, and Related frameworks links with no shared node. Seed Wallet Security from the pages that actually teach custody and signing. Cross-links to multisig, OpSec, and front-end come from shared controls, not related-to edges.
This was referenced Sep 14, 2026
mattaereal
added this pull request to stack #643
September 14, 2026 17:24
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What does this PR change?
Stacked on #633. Coverage work queue plus the first framework expansion: Wallet Security.
pnpm run coverage:security-mapprints threats with no control, controls with no guidance, frameworks with zero nodes, and## Related frameworkslinks whose slices share no graph node. It does not fail the build. Those bullets are not scraped intorelated-to.Wallet Security seed comes from pages that actually teach custody and signing (cold vs hot, seed phrase management, signing verification, contract interaction). The Hardware Wallets stub is not used as guidance. Cross-links to multisig, OpSec, and front-end appear because they share controls or
depends-onedges.Closes no issue.
Type of change
If applicable
vocs.config.tswith thedev: trueparameter