crate_interface
v0.3.0 GrowingProvides a way to define an interface (trait) in a crate, but can implement or use it in any crate.
Quick Verdict
- ✓Actively maintained (updated 58d ago)
- !Pre-1.0: API may have breaking changes
- ✓Team maintained (2 owners)
- ✓Tiny footprint (18KB, 3 deps)
- ✓Permissive license (Apache-2.0)
Security
Deep Insights
15.8K downloads in the last 30 days (527/day), up 104% from the previous period.
This crate is maintained by a team (2 owners), reducing bus-factor risk and ensuring continuity.
Despite being 2+ years old, crate_interface 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 17KB, crate_interface is lightweight. Small crate size correlates with focused, well-scoped functionality.
Notable dependents include kernel_guard, axplat-macros, axplat, axvisor_api, x86_vcpu. When high-quality crates choose crate_interface, 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 crate_interface
