# RUSTSEC-2022-0057: badge is Unmaintained

> The badge crate is unmaintained and deprecated, requiring users to migrate to supported alternatives to avoid supply chain risks.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not stated
- **Attackable:** Not stated
- **Victim action needed:** Not stated
- **Fix available:** No
- **Published:** 31 Aug 2022

## What is RUSTSEC-2022-0057?

RUSTSEC-2022-0057 is a vulnerability in badge, published on 31 Aug 2022. 

### Official description

The maintainer has advised this crate is deprecated and will not receive any maintenance.

The crate depends on the deprecated `rusttype` crate and won't receive updates
anymore.

## Possible Alternative(s)

 The below list has not been vetted in any way and may or may not contain alternatives;

 - [badge-maker](https://crates.io/crates/badge-maker)
 - [badgeland](https://crates.io/crates/badgeland)
 - [badgen](https://crates.io/crates/badgen)
 - [badgers](https://crates.io/crates/badgers) (API compatible fork of the `badge` crate using `ab_glyph` as a replacement for `rusttype`)
 - [rsbadges](https://crates.io/crates/rsbadges) (used deprecated `rusttype`)

## Which versions are affected by RUSTSEC-2022-0057?

1 open source package ship an affected version, including badge.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `badge` | crates.io | From 0.0.0-0 | None |

## How do I fix RUSTSEC-2022-0057?

No fix has been published for RUSTSEC-2022-0057 yet. Limit exposure of the affected software until one is available.

## Is RUSTSEC-2022-0057 being exploited?

There is no known exploitation of RUSTSEC-2022-0057 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for RUSTSEC-2022-0057 and fix it if it is affected.

What it is: RUSTSEC-2022-0057 is a vulnerability in badge, published on 31 Aug 2022. 
Exploitation: There is no known exploitation of RUSTSEC-2022-0057 in the wild and no public exploit code.

Affected packages and fixed versions:
- badge (crates.io): affected from 0.0.0-0; no fix listed

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/RUSTSEC-2022-0057/ (Markdown: https://insights.sbomify.com/RUSTSEC-2022-0057/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/RUSTSEC-2022-0057

---
From sbomify Insights: https://insights.sbomify.com/RUSTSEC-2022-0057/
Summaries are generated and may contain mistakes; the official description above is the record.