Cargo · crates.io

dockerfile-roast

Remote Payload

Why PkgRadar flagged 1.7.0

Severity	Signal
medium	Remote Payload ×3

Showing signal labels only. Sign in to view the exact matched indicators for each finding.

Scanned versions

Version	Verdict	Score	Scanned (UTC)
`1.7.0`	Review	24	2026-09-01
`1.6.1`	Review	24	2026-08-20
`1.6.0`	Review	24	2026-08-15
`1.5.1`	Review	24	2026-08-13
`1.5.0`	Review	24	2026-08-09
`1.4.13`	Review	24	2026-08-05
`1.4.12`	Review	14	2026-07-31
`1.4.8`	Review	1	2026-07-23
`1.4.7`	Low risk	0	2026-07-21
`1.4.5`	Low risk	0	2026-07-21
`1.4.4`	Low risk	0	2026-07-19
`1.4.3`	Low risk	0	2026-07-19
`1.4.2`	Low risk	0	2026-07-18
`1.4.1`	Low risk	0	2026-07-18

Verdict reflects the highest-severity signal, not just the additive score: a single high-severity finding outranks a higher score made up of lower-severity ones, so a lower-scored version can still carry the stronger verdict.

Block this in CI

PkgRadar gates dockerfile-roast (and every other dependency) before it merges. One line in your pipeline:

pkgradar gate --ecosystem cargo [email protected]

Prefer zero config? Install the GitHub App and it gates every pull request automatically — no pipeline edits, no API key.

Start free — 25 scans / mo View full evidence