wasmtimer
v0.4.3 GrowingTime utils from std::time, tokio::time and tokio_util::time on WASM targets
Quick Verdict
- !Pre-1.0: API may have breaking changes
- ✓Massive adoption (1.7K crates depend on it)
- ✓Permissive license (MIT)
Security
Deep Insights
859.3K downloads in the last 30 days (28.6K/day), up 36% from the previous period.
1.7K crates depend on wasmtimer. Strong ecosystem adoption means battle-tested code and long-term stability.
wasmtimer has only 1 owner despite 1.7K dependents. This is a bus-factor concern — consider the implications for long-term support.
Despite being 3+ years old, wasmtimer hasn't reached 1.0 yet. Expect potential API changes between versions.
At 37KB, wasmtimer is lightweight. Small crate size correlates with focused, well-scoped functionality.
Notable dependents include reqwest-retry, alloy-transport, alloy-rpc-client, alloy-provider, alloy-pubsub. When high-quality crates choose wasmtimer, 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
Version Adoption
Release Timeline
Feature Flags
default =["tokio", "tokio-util"]
