no cvss
—
RUSTSEC-2025-0048 json
tsify-next is unmaintained, use tsify instead
published last yr. modified last yr.
- cvss
- —
- not scored
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- —
- no score, EPSS covers CVEs only
- public exploits
- 0
- none known
Summary
The `tsify-next` crate is not maintained any more; use [`tsify`](https://crates.io/crates/tsify) instead.
Patch / fix
- github.com/siefkenj/tsify#56 pull request
Is RUSTSEC-2025-0048 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerAffected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| crates.io | tsify-next | >=0.0.0-0 |
no fix listed |
References
Sources
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.