failurecrates.io
- latest 0.1.8
- last known licence MIT OR Apache-2.0
- stars 1,413
- assessment attempted 25 days ago
- GitHub evidence observed 25 days ago
- registry checked 29 days ago
- registry ↗
- repository ↗
Vulnerabilities, end of life and next steps
Check a specific version for known advisories, documented mitigations and evidence-backed earlier-version options. Maintenance health is separate from vulnerability status.
Review remediation options →Maintenance trends
Loading historical repository activity…
Signals · last 17 checks
What the project says about itself
- OpenSSF Scorecard — 2.8 / 10 on 2026-08-24. Source: OpenSSF, via deps.dev. A third party's view of security practice, not part of the health score.
Third-party facts checked 25 days ago; registry facts on every crawl.
State history 1
| When | Change |
|---|---|
| 2026-10-21 | first verdict: abandoned |
Where to go instead 2
-
thiserror A few hours
For libraries: derives the error type failure used to
Replace `#[derive(Fail)]` with `#[derive(thiserror::Error)]` and implement `std::error::Error`.
Checked by hand.
-
anyhow Drop-in replacement
For applications: one boxed error type, like failure::Error
`failure::Error` becomes `anyhow::Error`, and `bail!`/`ensure!` keep working.
Checked by hand.
Badge
Drop this in your README. It re-renders itself as the verdict changes.
[](https://isitdeadyet.dev/crates/failure)Watch it
Get told when failure changes state, changes licence, or is deprecated — instead of finding out during an incident.
Free for up to 25 packages. Signing in is a link sent to your email — there is no password to choose.