Cargo · crates.io

locode-packs

Remote Payload

Why PkgRadar flagged 0.1.19

Severity	Signal
medium	Remote Payload

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

Scanned versions

Version	Verdict	Score	Scanned (UTC)
`0.1.19`	Review	12	2026-08-07
`0.1.18`	Review	4	2026-07-29
`0.1.17`	Review	2	2026-07-28
`0.1.16`	Review	2	2026-07-27
`0.1.15`	Review	3	2026-07-26
`0.1.14`	Review	3	2026-07-25
`0.1.13`	Review	3	2026-07-25
`0.1.7`	Low risk	0	2026-07-22
`0.1.6`	Low risk	0	2026-07-22
`0.1.5`	Low risk	0	2026-07-22
`0.1.4`	Low risk	0	2026-07-21
`0.1.3`	Low risk	0	2026-07-21
`0.1.2`	Low risk	0	2026-07-20
`0.1.1`	Low risk	0	2026-07-19
`0.1.0`	Low risk	0	2026-07-19

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 locode-packs (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