Contributions must preserve the crate's security posture.
Run:
scripts/checks.shFor release candidates, run:
scripts/stable_release_gate.sh- Do not add unsafe Rust.
- Do not log tokens, secret IDs, client tokens, wrapping tokens, passwords, or unwrapped secret payloads.
- Do not add an external dependency unless it removes meaningful risk or complexity.
- Validate every OpenBao path through the shared path helpers.
- Keep feature flags narrow and documented.
- Prefer explicit structs over untyped
serde_json::Valuein public APIs. - Use
serde_json::Valueonly for raw extension points or plugin payloads. - Add tests for both success and failure cases.
Before adding a dependency:
- Confirm the latest version.
- Confirm license compatibility with
MIT OR Apache-2.0. - Confirm the crate is maintained.
- Update
deny.tomlonly with a written reason in the release plan. - Run
cargo deny checkandcargo audit.
Every release must have:
- a release-notes file under
release-notes/; - a passing release gate;
- generated SBOM evidence;
- reviewed
cargo auditandcargo denyoutput; - owner-provided pentest report before tagging.