@readystack/sv-rechengroessen-lint-2026@1.0.4
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.
Findet in Lohn- und HR-Konfigurationsdateien jede Zeile, in der ein deutscher Sozialversicherungs-Wert aus 2025 steht, und nennt den ab 2026-01-01 gültigen Wert.
AI Security Review
scanned 5d ago · by lpm-firewall-aiThe package sends undisclosed runtime usage and paywall telemetry to its own service during interactive use. The event data is limited and has opt-outs, so this warrants a warning rather than a malicious verdict.
Static reason
High-risk behavior combination matched malicious policy.
Trigger
Starting an interactive free CLI run, or attempting a paid operation without a valid license; telemetry can be disabled with DO_NOT_TRACK=1 or READYSTACK_NO_TELEMETRY, and is skipped in CI.
Impact
The vendor learns that the package was used and whether a license was missing or rejected; no project contents or credentials are included in these event payloads.
Mechanism
The CLI posts product usage and paywall events to the vendor endpoint. License validation and the rules feed also contact their documented service endpoints.
AI rationale
The package sends undisclosed runtime usage and paywall telemetry to its own service during interactive use. The event data is limited and has opt-outs, so this warrants a warning rather than a malicious verdict.
Evidence
cli.jslicense.js~/.config/readystack/sv-rechengroessen-lint-2026.json (or READYSTACK_HOME/sv-rechengroessen-lint-2026.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 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 unless telemetry opt-outs or CI are detected.
- Missing or rejected license checks send a paywall event during interactive CLI or MCP use; its payload contains the product slug, source and reason.
- The README documents paid folder scans and licensing but does not disclose the usage events.
Evidence against
- The usage event payload is limited to the product slug, source and usage reason; it does not include project files, credentials or identifying machine details.
- License keys are sent to the package's licensing service for validation, consistent with the documented paid features.
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/sv-rechengroessen-lint-2026@1.0.4.
See all versions of @readystack/sv-rechengroessen-lint-2026 for other recorded verdicts.
- Review the evidence and your use of @readystack/sv-rechengroessen-lint-2026@1.0.4 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.