Cargo · crates.io

zakura

Remote Payload

Why PkgRadar flagged 1.3.0-rc4

Severity	Signal	Evidence
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)
`1.3.0-rc4`	Review	12	2026-08-28
`1.3.0-rc1`	Review	12	2026-08-22
`1.2.0`	Review	12	2026-08-14
`1.1.1`	Review	12	2026-08-10
`1.1.0`	Review	12	2026-08-05
`1.1.0-rc2`	Review	12	2026-08-05
`1.1.0-rc1`	Review	12	2026-08-02
`1.0.5`	Review	8	2026-07-28
`1.0.4`	Review	5	2026-07-25
`1.0.3`	Review	2	2026-07-22
`1.0.3-rc2`	Review	1	2026-07-22
`1.0.3-rc0`	Review	1	2026-07-22
`1.0.2`	Low risk	0	2026-07-20
`1.0.2-rc1`	Low risk	0	2026-07-20
`1.0.2-rc0`	Low risk	0	2026-07-19
`1.0.1`

Block this in CI

PkgRadar gates zakura (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.