zeroize
v1.8.2 GrowingSecurely clear secrets from memory with a simple trait built on stable Rust primitives which guarantee memory is zeroed using an operation will not be 'optimized away' by the compiler. Uses a portable pure Rust implementation that works everywhere, even WASM!
Quick Verdict
- ✓Stable API (1.x for 7+ years)
- ✓Massive adoption (21.2K crates depend on it)
- ✓Team maintained (2 owners)
- ✓Tiny footprint (21KB, 2 deps)
- ✓Permissive license (Apache-2.0 OR MIT)
Security
Deep Insights
36.1M downloads in the last 30 days (1.2M/day), up 15% from the previous period.
21.2K crates depend on zeroize — it's part of the Rust ecosystem's core infrastructure. Removing it from your dependency tree would be extremely difficult.
The primary maintainer publishes 215 crates. This suggests deep Rust expertise and long-term commitment to the ecosystem.
The API has been stable (1.x) for over 7 years with 45 releases. This level of maturity means you can depend on it without worrying about breaking changes.
Only 2 direct dependencies. Lean dependency tree means faster builds and lower supply chain risk.
At 20KB, zeroize is lightweight. Small crate size correlates with focused, well-scoped functionality.
60% of releases have been yanked. Check version history before pinning.
Notable dependents include digest, block-buffer, rustls, generic-array, arrayvec. When high-quality crates choose zeroize, it's a strong quality signal.
Health Breakdown
Recency, release consistency, active ratio
Yanked ratio, deps, size, maturity, features
Reverse deps, ownership, ecosystem
Downloads, momentum, growth trend
Docs, repo, license, metadata
Download Trend
Top Dependents
Most downloaded crates that depend on zeroize
Version Adoption
Release Timeline
Feature Flags
default =["alloc"]
