Skip to content

fix: add unsafe code guardrails#54

Merged
rickcrawford merged 1 commit intomainfrom
feat/wor-19-unsafe-guards
May 6, 2026
Merged

fix: add unsafe code guardrails#54
rickcrawford merged 1 commit intomainfrom
feat/wor-19-unsafe-guards

Conversation

@rickcrawford
Copy link
Copy Markdown
Contributor

Summary

  • Closes WOR-19 by adding #![forbid(unsafe_code)] to crate roots that do not need unsafe.
  • Adds an explicit #![allow(unsafe_code)] and inline justification for sbproxy-vault, where volatile zeroization intentionally uses unsafe.
  • Updates the unreleased changelog entry for the guardrail.

Test plan

  • cargo fmt --all -- --check
  • cargo build --workspace
  • cargo check --workspace --all-targets
  • IDE lints: no linter errors reported for edited crate roots

Made with Cursor

@rickcrawford rickcrawford force-pushed the feat/wor-19-unsafe-guards branch 4 times, most recently from cc63cf3 to 752a4af Compare May 6, 2026 05:45
Forbid unsafe in crates that do not require it and document the vault crate's explicit zeroization exception so future unsafe drift fails at compile time.

Co-authored-by: Cursor <cursoragent@cursor.com>
@rickcrawford rickcrawford force-pushed the feat/wor-19-unsafe-guards branch from 752a4af to 9f0a913 Compare May 6, 2026 07:39
@rickcrawford rickcrawford merged commit 5d4ac67 into main May 6, 2026
8 checks passed
@rickcrawford rickcrawford deleted the feat/wor-19-unsafe-guards branch May 6, 2026 07:58
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant