@readystack/cargo-publish-gate@1.0.5
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 sends limited runtime telemetry to its own service without disclosing it in the README, which meets the suspicious telemetry criterion. License validation and rule-feed requests send a user-provided license key to the package's own service and do not show credential theft.
Static reason
High-risk behavior combination matched malicious policy.
Trigger
A free interactive CLI scan, or a missing license key during a paid action or MCP check.
Impact
The vendor can observe package usage and paywall events. The payload does not include credentials or project contents.
Mechanism
Sends an event with the package slug, source, and reason to the vendor's /api/ev endpoint; opt-out and CI checks suppress it.
AI rationale
The package sends limited runtime telemetry to its own service without disclosing it in the README, which meets the suspicious telemetry criterion. License validation and rule-feed requests send a user-provided license key to the package's own service and do not show credential theft.
Evidence
cli.jslicense.js~/.config/readystack/cargo-publish-gate.json
Network endpoints3
getreadystack.com/api/evgetreadystack.com/api/lic?key=getreadystack.com/api/rules/
Decision evidence
public snapshotAI called this Suspicious at 90.0% confidence as Dangerous Capability with medium false-positive risk.
Evidence for warning
- After a free CLI scan, the program calls pingUse to report usage.
- The usage event contains the package slug, CLI source, and a free-use reason, and is sent to getreadystack.com/api/ev.
- When no license key is available, the package can send a paywall event to getreadystack.com/api/ev.
- The event sender supports opt-outs through DO_NOT_TRACK, READYSTACK_NO_TELEMETRY, and CI checks.
- License keys are sent to getreadystack.com for validation, the package's own service.
Evidence against
- The telemetry payloads contain event labels and package identifiers, not credentials, file contents, or project data.
- Usage telemetry is limited to interactive CLI runs; CI and explicit telemetry opt-outs suppress it.
- The README describes the CLI and licensing but does not disclose runtime telemetry.
Behavioral surface
EnvironmentVarsFilesystemNetwork
HighEntropyStringsUrlStrings
Source & flagged code
5 flaggedlicense.jsView file
2'use strict';
L3: const https = require('https'), fs = require('fs'), path = require('path'), os = require('os');
L4: const ORG_ID = '';
...
L9: const RECHECK_MS = 7 * 24 * 3600 * 1000; // re-ask Polar every 7 days (refunds / cancellations)
L10: function storePath() { return path.join(process.env.READYSTACK_HOME || path.join(os.homedir(), '.config', 'readystack'), SLUG + '.json'); }
L11: function load() { try { return JSON.parse(fs.readFileSync(storePath(), 'utf8')); } catch (e) { return {}; } }
L12: function save(o) { try { fs.mkdirSync(path.dirname(storePath()), { recursive: true }); fs.writeFileSync(storePath(), JSON.stringify(o)); } catch (e) { /* read-only home: still work...
...
L33: req.on('error', function () { resolve({ ok: false, offline: true }); });
L34: req.end();
L35: })
Critical
Credential Exfiltration
Source appears to send environment or credential material to an external endpoint.
license.jsView on unpkg · L22Trigger-reachable chain: manifest.bin -> cli.js -> license.js
L2: 'use strict';
L3: const https = require('https'), fs = require('fs'), path = require('path'), os = require('os');
L4: const ORG_ID = '';
...
L9: const RECHECK_MS = 7 * 24 * 3600 * 1000; // re-ask Polar every 7 days (refunds / cancellations)
L10: function storePath() { return path.join(process.env.READYSTACK_HOME || path.join(os.homedir(), '.config', 'readystack'), SLUG + '.json'); }
L11: function load() { try { return JSON.parse(fs.readFileSync(storePath(), 'utf8')); } catch (e) { return {}; } }
L12: function save(o) { try { fs.mkdirSync(path.dirname(storePath()), { recursive: true }); fs.writeFileSync(storePath(), JSON.stringify(o)); } catch (e) { /* read-only home: still work...
...
L33: req.on('error', function () { reso
Findings
2 Critical2 High4 Medium4 Low
CriticalCredential Exfiltrationlicense.js
CriticalTrigger Reachable Dangerous Capabilitylicense.js
HighSandbox Evasion Gated Capabilitylicense.js
HighTrigger Reachable Credential Exfiltrationlicense.js
MediumNetwork
MediumEnvironment Vars
MediumStructural Risk Force Deep Review
MediumAi Review Evidencecli.js
LowFilesystem
LowHigh Entropy Strings
LowUrl Strings
LowNo License
Affected versions and remediation
This report applies to @readystack/cargo-publish-gate@1.0.5.
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.5 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.