@readystack/cargo-publish-gate@1.0.3
Not affiliated with ReadyStack (readystack.dev). No new versions are published here. These tools continue under the name Rulestamp, by the team behind getreadystack.com.
Names every crates.io publish blocker in a Cargo.toml before the upload burns a version number.
AI Security Review
scanned 4d ago · by lpm-firewall-aiThe package performs undisclosed runtime telemetry to its own service during interactive use, despite providing opt-out variables. The event data is limited to package-use metadata, so this warrants a warning rather than a publish block.
Decision evidence
public snapshot- The CLI sends a usage event to getreadystack.com containing only the tool slug, CLI source and a fixed reason.
- A human TTY invocation can trigger the usage event after a free scan; DO_NOT_TRACK=1, READYSTACK_NO_TELEMETRY or CI disables it.
- The README describes the free and licensed features but does not disclose this usage reporting.
- The event contains no credentials, file contents, paths or environment values.
- Reporting is limited to interactive TTY use and has opt-out environment variables.
- The package is a Cargo manifest checker; its CLI reads files and runs local checks.
Source & flagged code
5 flaggedSource appears to send environment or credential material to an external endpoint.
license.jsView on unpkg · L2Findings
Affected versions and remediation
This report applies to @readystack/cargo-publish-gate@1.0.3.
See all versions of @readystack/cargo-publish-gate for other recorded verdicts.
- Review the evidence and your use of @readystack/cargo-publish-gate@1.0.3 before allowing it. Restrict the permissions described in this report.
- Choose an independently verified alternative or release. This report does not establish that other versions are safe.
Evidence last updated: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.