@readystack/loeschkonzept-fristen-lint@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.
BEG IV: Buchungsbelege 8 statt 10 Jahre — prüft jede Zeile Ihres Löschkonzepts gegen AO, HGB und DSGVO
AI Security Review
scanned 4d ago · by lpm-firewall-aiThe flagged network and environment access is used for the package’s licensing and limited usage reporting. The reviewed flows do not send unrelated credentials, project data or file contents to an external collector.
Static reason
High-risk behavior combination matched malicious policy.
Trigger
CLI invocation; license checks occur for paid operations or an explicit license command, and the usage counter runs during interactive free use.
Impact
No credential theft, unrelated collection, destructive action or code execution was found.
Mechanism
Sends license keys to the vendor’s license service and Polar for validation, and sends a limited usage event to the vendor. Cached license and feed data are stored locally.
AI rationale
The flagged network and environment access is used for the package’s licensing and limited usage reporting. The reviewed flows do not send unrelated credentials, project data or file contents to an external collector.
Evidence
${READYSTACK_HOME}/loeschkonzept-fristen-lint.json~/.config/readystack/loeschkonzept-fristen-lint.jsonuser-specified --out path
Network endpoints4
getreadystack.com/api/licgetreadystack.com/api/rules/getreadystack.com/api/evapi.polar.sh/v1/customer-portal/license-keys/validate
Decision evidence
public snapshotAI called this Clean at 96.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- The manifest exposes `cli.js` as the package command; it has no lifecycle scripts.
- The license module sends a supplied or stored license key to `getreadystack.com` for validation and to Polar’s license validation endpoint.
- The paywall counter sends only the package slug, CLI/MCP source and reason; it supports telemetry opt-outs and skips CI.
- At CLI startup, a stored license may be sent to the vendor’s rules-feed endpoint; returned rules are appended as data, while the engine uses its prebuilt ID map to produce lint findings.
- The CLI’s stated purpose and engine behavior are checking retention-period tables against AO, HGB and GDPR rules.
Evidence against
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 High3 Medium5 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
LowFilesystem
LowHigh Entropy Strings
LowUrl Strings
LowNo License
LowSuspicious Lifecycle Evidencepackage.json
Affected versions and remediation
This report applies to @readystack/loeschkonzept-fristen-lint@1.0.4.
See all versions of @readystack/loeschkonzept-fristen-lint for other recorded verdicts.
- Review the evidence and your use of @readystack/loeschkonzept-fristen-lint@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.