sanitize-filename
v0.6.0 GrowingA simple filename sanitizer, based on Node's sanitize-filename
Quick Verdict
- !Pre-1.0: API may have breaking changes
- ✓Massive adoption (1.9K crates depend on it)
- ✓Tiny footprint (5KB, 1 deps)
- ✓Permissive license (MIT)
Security
Deep Insights
469.8K downloads in the last 30 days (15.7K/day), up 13% from the previous period.
1.9K crates depend on sanitize-filename. Strong ecosystem adoption means battle-tested code and long-term stability.
sanitize-filename has only 1 owner despite 1.9K dependents. This is a bus-factor concern — consider the implications for long-term support.
Despite being 7+ years old, sanitize-filename hasn't reached 1.0 yet. Expect potential API changes between versions.
Only 1 direct dependencies. Lean dependency tree means faster builds and lower supply chain risk.
At 5KB, sanitize-filename is lightweight. Small crate size correlates with focused, well-scoped functionality.
Notable dependents include async_zip, cargo-generate, iai-callgrind-runner, burn-dataset, cubecl-common. When high-quality crates choose sanitize-filename, 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 sanitize-filename
