zbus
v5.14.0 StableAPI for D-Bus communication
Quick Verdict
- โActively maintained (updated 33d ago)
- โStable API (5.x for 5+ years)
- โMassive adoption (3.1K crates depend on it)
- !Heavy dependency tree (39 direct deps)
- โPermissive license (MIT)
Security
Deep Insights
4.9M downloads in the last 30 days (163.1K/day), up 26% from the previous period.
3.1K crates depend on zbus. Strong ecosystem adoption means battle-tested code and long-term stability.
zbus has only 1 owner despite 3.1K dependents. This is a bus-factor concern โ consider the implications for long-term support.
The API has been stable (1.x) for over 5 years with 87 releases. This level of maturity means you can depend on it without worrying about breaking changes.
39 direct dependencies. Consider the impact on compile times and supply chain complexity.
Notable dependents include opener, secret-service, keyring, ashpd, notify-rust. When high-quality crates choose zbus, 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 =["async-io", "blocking-api"]