pem-rfc7468
v1.0.0 GrowingPEM Encoding (RFC 7468) for PKIX, PKCS, and CMS Structures, implementing a strict subset of the original Privacy-Enhanced Mail encoding intended specifically for use with cryptographic keys, certificates, and other messages. Provides a no_std-friendly, constant-time implementation suitable for use with cryptographic private keys.
Quick Verdict
- ✓Stable API (1.x for 5+ years)
- ✓Trusted by 575 crates
- ✓Team maintained (2 owners)
- ✓Tiny footprint (25KB, 1 deps)
- ✓Permissive license (Apache-2.0 OR MIT)
Security
Deep Insights
20.6M downloads in the last 30 days, down 20% from the previous period. May indicate migration to alternatives.
575 crates depend on pem-rfc7468. Reasonable ecosystem adoption, though not yet a core dependency.
The primary maintainer publishes 220 crates. This suggests deep Rust expertise and long-term commitment to the ecosystem.
The API has been stable (1.x) for over 5 years with 23 releases. This level of maturity means you can depend on it without worrying about breaking changes.
Only 1 direct dependencies. Lean dependency tree means faster builds and lower supply chain risk.
At 25KB, pem-rfc7468 is lightweight. Small crate size correlates with focused, well-scoped functionality.
13% of releases have been yanked. Check version history before pinning.
Notable dependents include der, elliptic-curve, isahc, cms, ssh-encoding. When high-quality crates choose pem-rfc7468, 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
