@readystack/romu-hozon-kikan-lint-jp
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.
法定帳簿の保存期間を文書保存期間表で検査 — 労基法109条・安衛則51条・石綿則41条・雇用保険法施行規則143条・健保則34条（20 rules）
This report shows the evidence for @readystack/romu-hozon-kikan-lint-jp@1.0.3. 0 of 3 known versions are blocked or flagged. See all versions.
AI Security Review
scanned 4d ago · by lpm-firewall-aiThe flagged credential flow validates a user-supplied license key with the package’s licensing services and matches the CLI’s paid features. However, free interactive runs automatically send undisclosed usage telemetry to the vendor, which warrants a warning under the runtime telemetry rule.
Static reason
High-risk behavior combination matched malicious policy.
Trigger
A free CLI run in an interactive terminal; at most once per process.
Impact
The vendor learns that the CLI was used in free mode. The payload does not include credentials, file contents, paths, or user identity.
Mechanism
POSTs a small usage payload to getreadystack.com. The event is skipped when CI, DO_NOT_TRACK=1, or READYSTACK_NO_TELEMETRY is set.
AI rationale
The flagged credential flow validates a user-supplied license key with the package’s licensing services and matches the CLI’s paid features. However, free interactive runs automatically send undisclosed usage telemetry to the vendor, which warrants a warning under the runtime telemetry rule.
Evidence
cli.jslicense.js~/.config/readystack/romu-hozon-kikan-lint-jp.json (or the path configured by READYSTACK_HOME)
Network endpoints3
getreadystack.com/api/evgetreadystack.com/api/licapi.polar.sh/v1/customer-portal/license-keys/validate
Decision evidence
public snapshotAI called this Suspicious at 96.0% confidence as Dangerous Capability with low false-positive risk.
Evidence for warning
- Free CLI runs automatically send a first-party usage event containing the tool slug, CLI source, and free-use reason.
- The usage event runs only for unpaid runs in an interactive terminal and can be disabled with DO_NOT_TRACK=1 or READYSTACK_NO_TELEMETRY; README does not disclose this telemetry.
- A supplied license key is sent to the package vendor for license validation, consistent with the package’s paid features.
Evidence against
- The usage event contains no credentials, file contents, paths, or user identity in its payload.
- Telemetry is limited to one event per process and is skipped in CI or noninteractive runs.
- The package is a CLI for checking document-retention rules and describes its licensed folder-scan 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/romu-hozon-kikan-lint-jp@1.0.3.
The versions list below shows the verdict for each recorded version.
- Review the evidence and your use of @readystack/romu-hozon-kikan-lint-jp@1.0.3 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.