Cron Schedule Lint for crontab, Kubernetes CronJob, GitHub Actions, Spring and EventBridge
Runs the same checker as the npm package
@readystack/cron-schedule-linton a Node.js runtime that pip installs for you (nodejs-wheel-binaries) - no system Node.js needed. Your files are checked locally.
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.
Install
cron-schedule-lint file
Node 18+. The same 29 rules as the VS Code extension, from a terminal or CI.
Free
- Checks the file you have open against all 29 rules and, for every schedule line, prints the next three instants it really fires at, how many times it fires in a year, and the exact dates when that wall-clock time does not exist or happens twice - no key, no limit, no watermark.
--ruleslists every rule
With a licence ($29 once)
- Merges every schedule in the repository into one calendar instead of the single file you have open, exports it as CSV, JSON or HTML for a change review, and writes machine output a CI step can fail on so a merge cannot add a schedule that never fires.
@readystack/cron-schedule-lint --dir ./templates --report html --out report.html
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.
Use from an AI agent (MCP)
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 agent gets every finding with the line number.
Use in CI
- 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)
The folder sweep, reports and CI mode need one licence — one payment, no subscription. Set READYSTACK_LICENSE=<key> or run --license <key> once.
Install (PyPI)
pip install readystack-cron-schedule-lint
cron-schedule-lint --help
Metadata
Release files for readystack-cron-schedule-lint 0.1.9
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| readystack_cron_schedule_lint-0.1.9.tar.gz | 16.8 kB | Without provenance | Details for readystack_cron_schedule_lint-0.1.9.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| readystack_cron_schedule_lint-0.1.9-py3-none-any.whl | Python 3 | none | any | Details for readystack_cron_schedule_lint-0.1.9-py3-none-any.whl |
Total release size: 35.1 kB
Release files / readystack_cron_schedule_lint-0.1.9.tar.gz
| Download URL | readystack_cron_schedule_lint-0.1.9.tar.gz |
|---|---|
| Size | 16.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
872dd17d855538aad00ce029730599d260a9a3c48a260feeef5178c9c1c5a7ba
|
|
BLAKE2b-256 checksum How to use checksums |
f2b2eaa48e30f8804875253fc3e56fbe8ba49ea1af951f8fe480b66bd93777a2
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.12.3
|
Release files / readystack_cron_schedule_lint-0.1.9-py3-none-any.whl
| Download URL | readystack_cron_schedule_lint-0.1.9-py3-none-any.whl |
|---|---|
| Size | 18.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
09bdbd77a117560323df683d03f7cf79d47dcadbc31fc3d032b596ce53b42c32
|
|
BLAKE2b-256 checksum How to use checksums |
fff3b24a302f3328273ba685c57f8059f5224cc24e3a2e3d4843f2676d95bfc5
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.12.3
|
Security for readystack-cron-schedule-lint 0.1.9
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.