send_wrapper
v0.6.0 GrowingThis Rust library implements a wrapper type called SendWrapper which allows you to move around non-Send types between threads, as long as you access the contained value only from within the original thread. You also have to make sure that the wrapper is dropped from within the original thread. If any of these constraints is violated, a panic occurs.
Quick Verdict
- ✕Not updated for 3+ years
- !Pre-1.0: API may have breaking changes
- ✓Massive adoption (1.7K crates depend on it)
- ✓Team maintained (2 owners)
- ✓Tiny footprint (11KB, 3 deps)
Security
Deep Insights
2.5M downloads in the last 30 days (82.7K/day), up 32% from the previous period.
1.7K crates depend on send_wrapper. Strong ecosystem adoption means battle-tested code and long-term stability.
This crate is maintained by a team (2 owners), reducing bus-factor risk and ensuring continuity.
Despite being 8+ years old, send_wrapper hasn't reached 1.0 yet. Expect potential API changes between versions.
Only 3 direct dependencies. Lean dependency tree means faster builds and lower supply chain risk.
At 10KB, send_wrapper is lightweight. Small crate size correlates with focused, well-scoped functionality.
Notable dependents include pyo3, futures-timer, neon, ws_stream_wasm, libp2p-wasm-ext. When high-quality crates choose send_wrapper, 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 send_wrapper
