Rust advisories / static_type_map
UnmaintainedRUSTSEC-2022-0023 · static_type_map
RUSTSEC-2022-0023: `static_type_map` has been renamed to `erased_set`
Short answerNot a bug report: static_type_map is no longer maintained, so future security issues will not be fixed. Plan to move to a maintained alternative.
| Crate | static_type_map |
|---|---|
| Type | Unmaintained |
| Affected versions | Every version. |
| Fixed in | not applicable (the crate is unmaintained) |
| Severity | not scored |
| Published | 2022-05-11 |
| Last changed | 2022-05-11 |
| Also known as | none |
What to do
- Look for a maintained fork or alternative crate.
- If you cannot move yet, acknowledge it in your audit config so CI stays green while you plan: add
"RUSTSEC-2022-0023"toignorein.cargo/audit.tomlordeny.toml, with a comment saying why. - Find who pulls it in:
cargo tree -i static_type_map.
Details from the advisory
Please use the erased_set crate going forward:
<https://github.com/malobre/erased_set>
There will be no further releases of static_type_map.
References
- Package: crates.io/crates/static_type_map
- Advisory: rustsec.org/advisories/RUSTSEC-2022-0023.html
- Report: github.com/malobre/erased_set/issues/6
From the RustSec Advisory Database (CC0-1.0) via the OSV export, downloaded Oct 24, 2026. Severity score computed from the published CVSS vector.
Up next
Are you affected?Check your whole dependency treePaste Cargo.lock: every advisory, for your exact versions.Read it next →Also worth your time
Did this answer your question?