@readystack/audit-log-retention-lint@1.0.2
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.
Log retention lint for Loki, CloudWatch, ILM, S3 and Kubernetes audit YAML
AI Security Review
scanned 4d ago · by lpm-firewall-aiThe package sends runtime usage telemetry to its own service without disclosing it in the README. The fields are limited to product-use metadata and reporting has opt-out controls, so this warrants a warning rather than a block.
Static reason
High-risk behavior combination matched malicious policy.
Trigger
A free scan in an interactive terminal; paywall events can also be reported when a key is missing or rejected.
Impact
The publisher can count interactive usage and paywall outcomes; the reported fields do not include sensitive user or project data.
Mechanism
The CLI posts the event type, package slug, source and reason to getreadystack.com/api/ev. Environment-variable controls and non-interactive execution suppress the report.
AI rationale
The package sends runtime usage telemetry to its own service without disclosing it in the README. The fields are limited to product-use metadata and reporting has opt-out controls, so this warrants a warning rather than a block.
Evidence
cli.jslicense.jsREADME.md
Network endpoints4
getreadystack.com/api/evgetreadystack.com/api/licapi.polar.sh/v1/customer-portal/license-keys/validategetreadystack.com/api/rules/
Decision evidence
public snapshotAI called this Suspicious at 93.0% confidence as Dangerous Capability with medium false-positive risk.
Evidence for warning
- A free CLI run reports usage to getreadystack.com with only the event type, package slug, source and reason; the README does not disclose this telemetry.
- The usage report runs after a free scan, and is limited to interactive terminal sessions unless disabled by environment variables.
- License checks and rule-feed requests are tied to the package’s licensing function and its own service.
Evidence against
- The reported usage fields contain no credentials, file contents, paths, hostnames or usernames.
- Telemetry is suppressed by DO_NOT_TRACK=1, READYSTACK_NO_TELEMETRY or CI, and is not sent in non-interactive CLI runs.
- The package is a CLI lint tool, and its README describes free checks and licensed workspace scans.
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
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/audit-log-retention-lint@1.0.2.
See all versions of @readystack/audit-log-retention-lint for other recorded verdicts.
- Review the evidence and your use of @readystack/audit-log-retention-lint@1.0.2 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.