@readystack/romu-hozon-kikan-lint-jp@1.0.3
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)
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.
Decision evidence
public snapshot- 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.
- 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.
Source & flagged code
5 flaggedSource appears to send environment or credential material to an external endpoint.
license.jsView on unpkg · L2Findings
Affected versions and remediation
This report applies to @readystack/romu-hozon-kikan-lint-jp@1.0.3.
See all versions of @readystack/romu-hozon-kikan-lint-jp for other recorded verdicts.
- 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.