X0019 deny-advisories¶
Rule: No dependency has a security advisory, is unmaintained, unsound or yanked.
| Code | X0019 (stable, never reused) |
| Id | deny-advisories |
| Category | deny |
| Source | cargo-deny (run as an executable) |
| Fix | by hand |
| Needs | cargo-deny installed |
Level per tier¶
| Tier | Level | Reason |
|---|---|---|
| small | warn |
a dependency with a known vulnerability is a risk taken unseen; needs no deny.toml |
| small-workspace | warn |
a dependency with a known vulnerability is a risk taken unseen; needs no deny.toml |
| medium | deny |
a vulnerable dependency is updated, or its advisory ignored with a reason in deny.toml |
| big | deny |
a vulnerable dependency is updated, or its advisory ignored with a reason in deny.toml |
| ai | off | |
| embedded | off | |
| ui | off | |
| egui | off | |
| units-strict | off | |
| units-paranoid | off |
Parameters¶
| Name | Type | Default | Meaning |
|---|---|---|---|
fetch |
boolean | true |
update the advisory database first; false checks against the local copy (--offline) |
Why¶
A dependency with a known vulnerability, an unsound API, an unmaintained crate or a yanked version is a risk the project takes on without seeing it. cargo-deny checks the graph against the RustSec advisory database; this lint reports what it finds.
How to fix¶
Update the crate to a fixed version (cargo update -p NAME), or replace it. An advisory that does not apply goes into deny.toml with its reason:
Configure¶
[lints.deny-advisories]
level = "deny"
fetch = true
reason = "why this project wants it at this level"
Allow one finding in the code with // spirit-level: allow(deny-advisories) <reason> (waivers); the code works there too, as in [lints.X0019].