anyhow
Cargov1.0.104Flexible concrete Error type built on std::error::Error
Not recommended for new projects
No — anyhow should not be adopted for new projects. No license declared — you have no explicit right to use this code.
- ?Adoption: grade ?, Not reported by this registry.
No download data reported for this package yet.
- AMaintenance: grade A, Excellent.
Last published 53 days ago. 17 releases in the last 2 years.
- AWeight: grade A, Excellent.
Zero runtime dependencies.
- BSupply chain: grade B, Good.
This package has a single maintainer (bus factor of 1).
- FLicense: grade F, Failing.
No license declared — you have no explicit right to use this code.
Grades are computed deterministically from registry metadata collected by PackageGraph — downloads, dependents, publish dates, the resolved dependency tree, maintainer count, and declared licenses. No third-party scores are used.
Install cost
What you actually take on by adding anyhow to a project.
Runtime packages this one declares itself.
Distinct packages in the full runtime tree, deduplicated the way a package manager would.
Unpacked size of this package plus its entire runtime tree.
Longest resolved dependency chain below this package.
Compatibility
- Rust edition
- No constraint declared
anyhow vs the alternatives
Packages solving a similar problem in the cargo ecosystem, compared on the signals that drive an adoption decision.
| Package | Weekly downloads | Dependents | License | Last release |
|---|---|---|---|---|
| anyhowthis page | 0 | 0 | — | 1 month ago |
| thiserror | 0 | 0 | — | 1 day ago |
Release history
11 releases in the last two years, typically about 23 days apart.
| Version | Published | Size | License |
|---|---|---|---|
| 1.0.104latest | 1 month ago | — | MIT OR Apache-2.0 |
| 1.0.103 | 2 months ago | — | MIT OR Apache-2.0 |
| 1.0.102 | 6 months ago | — | MIT OR Apache-2.0 |
| 1.0.101 | 7 months ago | — | MIT OR Apache-2.0 |
| 1.0.100 | 11 months ago | — | MIT OR Apache-2.0 |
| 1.0.99 | 1 year ago | — | MIT OR Apache-2.0 |
| 1.0.98 | 1 year ago | — | MIT OR Apache-2.0 |
| 1.0.97 | 1 year ago | — | MIT OR Apache-2.0 |
| 1.0.96 | 1 year ago | — | MIT OR Apache-2.0 |
| 1.0.95 | 1 year ago | — | MIT OR Apache-2.0 |
| 1.0.94 | 1 year ago | — | MIT OR Apache-2.0 |
| 1.0.93 | 1 year ago | — | MIT OR Apache-2.0 |
| 1.0.92 | 1 year ago | — | MIT OR Apache-2.0 |
| 1.0.91 | 1 year ago | — | MIT OR Apache-2.0 |
| 1.0.90 | 1 year ago | — | MIT OR Apache-2.0 |
Overview
anyhow is an Cargo package that flexible concrete Error type built on std::error::Error. The latest version is 1.0.104.
Who should use it
Teams working in the Cargo ecosystem who need flexible concrete Error type built on std::error::Error and value a focused solution.
When not to use it
Consider an alternative if you need to or if a more actively-maintained option better fits your Cargo stack.
Pros
- Zero runtime dependencies — minimal footprint.
Cons
- No license detected — review usage terms before adopting.
Auto-generated from collected registry metadata. No external claims are inferred.
Maintainers
Keywords
Frequently asked questions
Should I use anyhow?
No — anyhow should not be adopted for new projects. No license declared — you have no explicit right to use this code.
How do I install anyhow?
Run `cargo add anyhow` to add anyhow to your Cargo project.
What license is anyhow released under?
No license was detected in anyhow's metadata; review the repository before use.
Is anyhow still maintained?
The most recent release of anyhow (v1.0.104) was published 1 month ago.