@readystack/vagrantfile-eol-box-lint
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.
6 findings in 1 file: boxes past end of support, with the date and the box to move to
This report shows the evidence for @readystack/vagrantfile-eol-box-lint@1.0.1. 0 of 2 known versions are blocked or flagged. See all versions.
AI Security Review
scanned 3d ago · by lpm-firewall-aiThe package performs undisclosed runtime telemetry during eligible CLI use, so it merits a warning under the telemetry rule. The event data is limited to product and usage labels, and the source does not show credential or file-content exfiltration.
Static reason
High-risk behavior combination matched malicious policy.
Trigger
A free CLI run, or a paid operation with a missing or invalid license, in an eligible CLI or MCP session.
Impact
The publisher can count eligible uses and paywall outcomes. The observed events do not include credentials or scanned file contents.
Mechanism
The CLI posts product slug, source, and event reason to https://getreadystack.com/api/ev. CI and opt-out environment variables suppress the paywall ping; the free-run ping also has terminal and opt-out checks.
AI rationale
The package performs undisclosed runtime telemetry during eligible CLI use, so it merits a warning under the telemetry rule. The event data is limited to product and usage labels, and the source does not show credential or file-content exfiltration.
Evidence
cli.jslicense.js~/.config/readystack/vagrantfile-eol-box-lint.json (or the path under READYSTACK_HOME)
Network endpoints4
getreadystack.com/api/evgetreadystack.com/api/licgetreadystack.com/api/rules/api.polar.sh/v1/customer-portal/license-keys/validate
Decision evidence
public snapshotAI called this Suspicious at 94.0% confidence as Dangerous Capability with medium false-positive risk.
Evidence for warning
- A free CLI run calls a usage ping that posts the product slug, CLI source, and event reason to the publisher’s /api/ev endpoint.
- A missing or invalid license can trigger a paywall event containing the product slug, source, and reason.
- The paywall ping is suppressed by CI and documented-in-code opt-out environment variables; eligible CLI or MCP sessions otherwise send it.
- The license value comes from an explicit argument, READYSTACK_LICENSE, or the package’s local cache, and is used for license validation.
- The package’s main function is local Vagrantfile scanning; the telemetry payloads do not include scanned file contents or unrelated credentials.
Evidence against
- The telemetry fields are limited to event labels and product context, with no hostname, username, paths, or file contents shown in the payloads.
- License validation sends the package’s own license key to getreadystack.com and Polar, consistent with the documented paid feature.
- The manifest exposes a CLI binary and has no lifecycle scripts.
Behavioral surface
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 = 'a5cdf664-d8e7-4f87-8895-056717aaba17';
...
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:
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 = 'a5cdf664-d8e7-4f87-8895-056717aaba17';
...
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
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/vagrantfile-eol-box-lint@1.0.1.
The versions list below shows the verdict for each recorded version.
- Review the evidence and your use of @readystack/vagrantfile-eol-box-lint@1.0.1 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.