@readystack/cron-schedule-lint@0.1.8
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 package exposes a CLI and has no lifecycle hook in the inspected manifest. The flagged network and credential behavior is tied to product licensing, rule updates, and opt-out-aware usage reporting, with no confirmed attack surface.
Decision evidence
public snapshot- The manifest exposes a CLI entry point; the inspected CLI performs its rule-feed check when it starts.
- The feed uses a supplied or stored license key and requests rules from the publisher’s product domain.
- The license key is also sent to Polar’s license-validation endpoint.
- Usage pings contain product and event labels, run only on a free CLI path, and are suppressed by telemetry opt-outs, CI, or non-interactive use.
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.8.
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.8 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.