@readystack/cron-schedule-lint@0.1.7
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.
Names every schedule line in the file you have open that fires at the wrong hour, twice, or never at all - and prints the next three times each one really fires, in the zone that actually applies.
AI Security Review
scanned 11d ago · by lpm-firewall-aiThe manifest points to a CLI and contains no lifecycle hook. The inspected network requests support license validation, the package’s rules feed, and guarded product-use telemetry; no concrete attack behavior was found.
Decision evidence
public snapshot- package.json exposes cli.js as the command entrypoint and declares no lifecycle scripts.
- cli.js invokes the rules feed; license.js sends a stored license key to the package’s rules-feed service when its cache expires.
- license.js validates license keys with Polar; the rules-feed request is used to retrieve rules.
- Usage telemetry sends a product-use event only when telemetry is enabled and the CLI is running interactively.
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/cron-schedule-lint@0.1.7.
See all versions of @readystack/cron-schedule-lint for other recorded verdicts.
- Review the evidence and your use of @readystack/cron-schedule-lint@0.1.7 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.