@readystack/privacidad-chile-21719-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.
Revisa la política de privacidad de un sitio chileno contra el art. 14 ter de la Ley 21.719 (rige el 2026-12-01)
AI Security Review
scanned 4d ago · by lpm-firewall-aiThe package sends runtime usage telemetry to its vendor by default during interactive runs, without disclosing it in the README. The events contain limited product-use fields and have opt-out controls, so this is suspicious telemetry rather than malicious data exfiltration.
Static reason
High-risk behavior combination matched malicious policy.
Trigger
Running the CLI in a terminal without the telemetry opt-out; a separate paywall event can be sent when a license key is missing or rejected.
Impact
The vendor can count interactive usage and paywall events. No user, project, file or credential data is included in these telemetry events.
Mechanism
HTTPS POST events contain the package slug, CLI or MCP source, and a fixed event reason. The license feed and validation also send the license key to their respective service endpoints.
AI rationale
The package sends runtime usage telemetry to its vendor by default during interactive runs, without disclosing it in the README. The events contain limited product-use fields and have opt-out controls, so this is suspicious telemetry rather than malicious data exfiltration.
Evidence
cli.jslicense.jsREADME.md~/.config/readystack/privacidad-chile-21719-lint.json (or READYSTACK_HOME/privacidad-chile-21719-lint.json)
Network endpoints3
getreadystack.com/api/evgetreadystack.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
- Interactive free CLI runs send a usage event to getreadystack.com containing only the tool slug, source and a fixed reason; the README does not disclose this telemetry.
- The usage event is gated to terminal sessions and can be disabled with DO_NOT_TRACK=1 or READYSTACK_NO_TELEMETRY, but it runs by default otherwise.
Evidence against
- The package is a privacy-policy lint CLI; its file scanning and license-gated reports match that purpose.
- The telemetry payload contains no file contents, credentials, hostname, username or project path.
- License validation and subscription-rule retrieval contact Polar or the package vendor for their stated licensing functions.
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...
...
L31: 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...
...
L31
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/privacidad-chile-21719-lint@1.0.2.
See all versions of @readystack/privacidad-chile-21719-lint for other recorded verdicts.
- Review the evidence and your use of @readystack/privacidad-chile-21719-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.