Install
$ agentstack add skill-yue-zhou1-zkcrypto-audit-rust-crypto-safety ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
rust-crypto-safety
Implementation-safety auditor for cryptographic Rust code.
When to Use
- Auditing Rust crates that implement or wrap cryptographic primitives
- Reviewing secret handling, constant-time behavior, and memory lifecycle
- Checking
unsafe, raw pointers,_uncheckedentrypoints, or manual concurrency traits - Reviewing cargo features, dependencies, and panic/error behavior on crypto paths
When NOT to Use
- Building protocol context before the code paths are identified
- Reviewing circuit constraints or verifier equations in ZK systems
- Declaring a finding confirmed without end-to-end verification
Core Review Areas
- Secret-dependent control flow and memory access
- Secret lifecycle and zeroization
unsafe, unchecked constructors, and trait soundness- Panic, overflow, cast, and feature-flag hazards
- Supply-chain and tool-assisted review
Workflow
Phase 1: Checklist pass
- Read
references/rust-checklist.md - Trace secret-bearing types through parsing, arithmetic, cloning, sharing, and drop paths
- Mark every
unsafe,_unchecked,unwrap,expect, andascast on the critical path
Phase 2: Pattern hunt
- Read
references/finding-patterns.md - Treat secret-dependent timing, zeroization gaps, unsafe deserialization, and unsound
Send/Syncas active search targets - Check feature-flagged code separately; hidden security semantics count as real audit surface
Phase 3: Tool-assisted review
- Read
references/toolchain.md - Run the smallest relevant tool set for the crate under review: static analysis first, then fuzzing, side-channel checks, and dependency inspection
- Use
audit-commontesting evidence language when describing gaps in coverage or missing negative tests
Phase 4: Handoff
- Send suspected findings to
crypto-fp-check - Use
zkbugs-indexonly after the finding survives verification and is suitable for indexing
Output Contract
Produce an implementation-safety handoff that includes:
- The relevant secret-bearing types, unsafe paths, or dependency surfaces
- Concrete timing, zeroization, panic, cast, or concurrency hazards observed
- Tool-assisted evidence already gathered
- The next verification or reporting route
Reference Index
- [references/rust-checklist.md](references/rust-checklist.md)
- [references/finding-patterns.md](references/finding-patterns.md)
- [references/toolchain.md](references/toolchain.md)
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: Yue-Zhou1
- Source: Yue-Zhou1/zkcrypto-audit
- License: MIT
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.