@readystack/kani-kazei-shokuhin-1pct-lint-jp@1.0.1
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.
売上帳CSVの税率と事業区分を検査し、1%特例込みで納付税額を概算
AI Security Review
scanned 5d ago · by lpm-firewall-aiThe CLI sends default runtime usage telemetry to the vendor after an interactive free scan, but the README does not disclose it. The payload is limited to package usage fields and has opt-out controls, so this warrants a warning rather than a malicious verdict.
Decision evidence
public snapshot- An interactive free CLI run automatically sends a usage event containing the package slug, CLI source and a fixed reason to getreadystack.com.
- The event is sent by default for TTY sessions; the README does not disclose this runtime telemetry.
- The event is limited to usage metadata and can be disabled with DO_NOT_TRACK=1 or READYSTACK_NO_TELEMETRY; it is also skipped in CI and non-TTY sessions.
- The package is a user-invoked CLI for scanning files, and the telemetry runs after a free scan rather than during installation.
- The inspected telemetry payload contains no file contents, credentials, hostnames, usernames or environment values.
- The license feed sends a configured package license key to getreadystack.com, the package's own service, for rule updates.
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/kani-kazei-shokuhin-1pct-lint-jp@1.0.1.
See all versions of @readystack/kani-kazei-shokuhin-1pct-lint-jp for other recorded verdicts.
- Review the evidence and your use of @readystack/kani-kazei-shokuhin-1pct-lint-jp@1.0.1 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.