Cargo · crates.io

code-steps-macros

Yanked Release, Cargo Proc Macro Crate

Why PkgRadar flagged 0.1.0

Severity	Signal	Evidence
medium	Yanked Release	—

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

Scanned versions

Version	Verdict	Score	Scanned (UTC)
`0.5.0`	Low risk	0	2026-07-11
`0.4.8`	Low risk	0	2026-07-11
`0.2.0`	Low risk	0	2026-07-11
`0.2.1`	Low risk	0	2026-07-11
`0.2.2`	Low risk	0	2026-07-11
`0.3.0`	Low risk	0	2026-07-11
`0.4.0`	Low risk	0	2026-07-11
`0.4.3`	Low risk	0	2026-07-11
`0.4.4`	Low risk	0	2026-07-11
`0.4.5`	Low risk	0	2026-07-11
`0.4.6`	Low risk	0	2026-07-11
`0.4.7`	Low risk	0	2026-07-11
`0.4.2`	Low risk	0	2026-07-11
`0.1.1`	Low risk	0	2026-07-11
`0.1.0`	Review	15	2026-07-11

Block this in CI

PkgRadar gates code-steps-macros (and every other dependency) before it merges. One line in your pipeline:

pkgradar gate --ecosystem cargo [email protected]