- 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 `zantetsu-trainer` crate is no longer maintained. The ML training infrastructure it contained was removed as part of the zantetsu 0.2 release, which replaced the neural parser with a pure heuristic engine.
A tombstone version (0.2.0) has been published and 0.1.4 has been yanked. There is no replacement for `zantetsu-trainer`.
## Migration
If you were using `zantetsu-trainer` as part of a zantetsu-based filename parsing pipeline, switch to [`zantetsu 0.2`](https://crates.io/crates/zantetsu), which requires no training step.
Is RUSTSEC-2026-0083 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 | zantetsu-trainer | >=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.