Names every schedule line in the file you have open that fires at the wrong hour, twice, or never at
175
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.
docker run --rm -v "$PWD":/work getreadystack/cron-schedule-lint /work/file
The same 29 rules as the VS Code extension, in a container. Mount a folder on /work.
--rules lists every ruledocker run --rm -e READYSTACK_LICENSE=<key> -v "$PWD":/work getreadystack/cron-schedule-lint --dir /work --ci
Healthchecks.io Business, the ordinary cron monitor, is $20 every month for 100 jobs - $240 a year, forever - and by design it can only tell you after a run was already missed.
Claude Code · Cursor · Windsurf · any MCP client - add to your MCP config:
{ "mcpServers": { "cron-schedule-lint": { "command": "npx", "args": ["-y", "@readystack/cron-schedule-lint", "--mcp"] } } }
Tools: check_text and check_file (free) · check_dir (licence; the full sweep is free for 7 days). The agent gets every finding with the line number.
- name: Cron Schedule Lint for crontab, Kubernetes CronJob, GitHub Actions, Spring and EventBridge
run: npx -y @readystack/cron-schedule-lint --dir . --ci
(container: docker run --rm -v "$PWD:/work" getreadystack/cron-schedule-lint --dir /work --ci)
Try the full run free for 7 days — no key needed. Then one licence, 7-day refund, no questions. Set READYSTACK_LICENSE=<key> or run --license <key> once.
Content type
Image
Digest
sha256:ca199014f…
Size
46.1 MB
Last updated
4 days ago
docker pull getreadystack/cron-schedule-lint