@readystack/openapi-security-contract-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.
Finds the lines in an OpenAPI file that publish an endpoint with no authentication, an API key in the query string, or an OAuth grant RFC 9700 forbids.
This report shows the evidence for @readystack/openapi-security-contract-lint@1.0.6. 0 of 5 known versions are blocked or flagged. See all versions.
AI Security Review
scanned 5d ago · by lpm-firewall-aiThe package sends undisclosed, anonymous runtime telemetry to its own service during interactive use. This meets the warning-only telemetry criterion; the license key traffic is part of the documented licensing flow.
Static reason
High-risk behavior combination matched malicious policy.; previous stored version diff introduced dangerous source
Trigger
A free CLI run with a TTY, or a licensing check that lacks or rejects a key; telemetry can be disabled with DO_NOT_TRACK=1 or READYSTACK_NO_TELEMETRY.
Impact
The publisher can count free usage and paywall events. No credential or project data is included in the telemetry payload.
Mechanism
The CLI posts a package slug, source, and event reason to the publisher's /api/ev endpoint. License validation also sends the provided license key to the publisher's licensing endpoint and Polar for validation.
AI rationale
The package sends undisclosed, anonymous runtime telemetry to its own service during interactive use. This meets the warning-only telemetry criterion; the license key traffic is part of the documented licensing flow.
Evidence
cli.jslicense.jsREADME.md~/.config/readystack/openapi-security-contract-lint.json
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 91.0% confidence as Dangerous Capability with medium false-positive risk.
Evidence for warning
- A free CLI run sends a usage event containing only the package slug, CLI source, and free-use reason to getreadystack.com when attached to a terminal; environment variables can disable it.
- The README describes free and licensed features but does not disclose the usage telemetry.
Evidence against
- The telemetry payload contains no credentials, file contents, hostnames, or usernames.
- The package uses the supplied license key to validate licensing with its own service and Polar.
- The manifest declares no lifecycle scripts, and the CLI's stated purpose is OpenAPI security linting.
Behavioral surface
EnvironmentVarsFilesystemNetwork
HighEntropyStringsUrlStrings
NoLicense
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
3 Critical2 High3 Medium4 Low
CriticalCredential Exfiltrationlicense.js
CriticalTrigger Reachable Dangerous Capabilitylicense.js
CriticalPrevious Version Dangerous Deltacli.js
HighSandbox Evasion Gated Capabilitylicense.js
HighTrigger Reachable Credential Exfiltrationlicense.js
MediumNetwork
MediumEnvironment Vars
MediumStructural Risk Force Deep Review
LowFilesystem
LowHigh Entropy Strings
LowUrl Strings
LowNo License
Affected versions and remediation
This report applies to @readystack/openapi-security-contract-lint@1.0.6.
The versions list below shows the verdict for each recorded version.
- Review the evidence and your use of @readystack/openapi-security-contract-lint@1.0.6 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.