# GHSA-vfv3-9w6v-23jp: typemap is Unmaintained

> The typemap library is unmaintained, posing supply chain risks due to lack of updates and potential incompatibility with future Rust versions.

- **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:** 6 Apr 2019
- **Also known as:** RUSTSEC-2019-0039

## What is GHSA-vfv3-9w6v-23jp?

GHSA-vfv3-9w6v-23jp is a vulnerability in typemap, published on 6 Apr 2019. 

### Official description

The maintainer seems unreachable.

The crate may or may not be usable as-is despite no maintenance and may not work in future versions of Rust.

The last release seems to have been seven years ago.

## Possible Alternative(s)

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

 - [ttmap](https://crates.io/crates/ttmap)
 - [typemap_rev](https://crates.io/crates/typemap_rev)
 - [typemap-ors](https://crates.io/crates/typemap-ors)

## Which versions are affected by GHSA-vfv3-9w6v-23jp?

3 open source packages ship an affected version, including typemap.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `typemap` | crates.io | All versions | None |
| `typemap` | crates.io | All versions | None |
| `typemap` | crates.io | From 0.0.0-0 | None |

## How do I fix GHSA-vfv3-9w6v-23jp?

No fix has been published for GHSA-vfv3-9w6v-23jp yet. Limit exposure of the affected software until one is available.

## Is GHSA-vfv3-9w6v-23jp being exploited?

There is no known exploitation of GHSA-vfv3-9w6v-23jp in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for GHSA-vfv3-9w6v-23jp and fix it if it is affected.

What it is: GHSA-vfv3-9w6v-23jp is a vulnerability in typemap, published on 6 Apr 2019. 
Exploitation: There is no known exploitation of GHSA-vfv3-9w6v-23jp in the wild and no public exploit code.

Affected packages and fixed versions:
- typemap (crates.io): affected all versions; no fix listed
- typemap (crates.io): affected all versions; no fix listed
- typemap (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/GHSA-vfv3-9w6v-23jp/ (Markdown: https://insights.sbomify.com/GHSA-vfv3-9w6v-23jp/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/GHSA-vfv3-9w6v-23jp

---
From sbomify Insights: https://insights.sbomify.com/GHSA-vfv3-9w6v-23jp/
Summaries are generated and may contain mistakes; the official description above is the record.