Running cronlint via npx is super convenient for quick checks without a full install. The output is clear and helps me spot issues like the never-fires error instantly. I like that I can pipe my crontab directly into it. It’s a handy little tool for keeping my scheduled jobs on track. The documentation is straightforward, and the MIT license is a plus. Seems like a great way to validate cron expressions before deployment.
Questions about cronlint
What is cronlint?
It is a zero-dependency command-line tool created by René Peter that lints cron expressions to detect schedule problems like dates that never fire or jobs that run excessively. It can be installed globally via npm or run without installation using npx, and it accepts a single cron expression or input piped from a crontab. The tool provides several output formats, including compact, GitHub annotation, and JSON, and supports options for evaluating daylight saving time rules against specific time zones and for treating warnings as errors in strict mode. It is distributed under the MIT license.
Which rules does cronlint check and how do I run it without installing?
The tool currently supports thirteen specific rules, including never-fires, step-invalid, dom-unreachable-months, dom-dow-both, star-minute-restricted, dst-ambiguous, range-wrap, freq-extreme, leap-day-only, nonportable-shortcut, redundant-term, step-uneven, and dow-sunday-7. Users can run it against a crontab by piping the output of crontab -l into cronlint - to lint every line. It also allows running without installation using npx @zbcdo/cronlint followed by the expression in quotes.
How can I configure cronlint to handle daylight saving time and integrate it with CI tools?
The tool can be used to evaluate daylight saving time rules against a specific zone using the --tz flag, such as America/New_York. It also supports a --strict flag to make warnings fail the command. The output can be formatted as JSON for machine-readable diagnostics or as GitHub annotations for CI pipelines. These features make it useful for developers integrating cron validation into their build processes.
What are the licensing terms and how can I get started with the tool?
The tool is free to use and distributed under the MIT license, which allows for open-source contributions and modification. It is available as a global npm package or via npx, requiring no additional dependencies. The website offers a live try-it feature at cronhelp.me where users can paste an expression to see every finding explained. The documentation is hosted at cronhelp.me/rules/never-fires.
Who created cronlint and who is the target audience for this tool?
The tool was created by René Peter and is hosted on the domain cronlint.org. It is designed for developers and system administrators who need to validate cron expressions before deploying them. The tool can be run locally on any machine with Node.js and npm installed, or via npx without a global installation.
What output formats are available and how do they help in different workflows?
The tool provides a --format github option to output annotation-style results for GitHub Actions CI, which helps developers catch cron errors early in the development process. It also supports a --format compact option that outputs one line per finding, which is useful for scripting and parsing logs. The JSON output format allows for programmatic consumption of the linting results.
What is the official website of cronlint?
The official website of cronlint is cronlint.org.
How is cronlint rated on Trustburn?
On Trustburn, cronlint has a rating of 3.5 out of 5 based on 4 reviews.
AI-generated from reviews on this page. Verify anything important with the company directly.
From the information available, cronlint appears to be a dedicated solution for validating cron expressions, focusing on specific rules that cause silent failures. The example provided regarding the 30th of February is a classic edge case that this tool catches well. The support for various output formats, including JSON and GitHub annotations, makes it versatile for different development environments. However, it is worth noting that there are thirteen rules so far. While this covers many common issues like DST ambiguity and leap days, it is unclear if the rule set is comprehensive enough for all edge cases in every time zone. The live demo on cronhelp.me is a nice touch for testing, but for production use, one might want more assurance that all possible scheduling errors are covered. It seems like a promising start, but the scope of coverage is not entirely defined in the available text.
I am looking at the site and it is hard to tell if this is free or paid. The MIT license suggests open source, but there is no clear pricing table or tier information. For someone considering this company, the lack of clarity on costs is a bit concerning. It would be helpful to know if there are premium features or if the npm package is the complete offering.
The tool seems very useful for catching those subtle errors in cron expressions that often go unnoticed until a job fails silently. The ability to lint individual expressions or pipe them from a crontab list is a strong feature. I appreciate the multiple output formats, especially the GitHub annotation style for CI workflows. It covers thirteen rules so far, which addresses common pitfalls like the never-fires issue on the 30th of February. Using it with a strict mode ensures warnings also fail the build, adding an extra layer of reliability. It appears to be a solid utility for anyone managing scheduled tasks who wants to prevent silent failures before they happen.
News
No news yet. This is where the business shares its own updates and press.
Photos
No photos yet. Photos shared by reviewers will show up here.
Widgets
Get the widget for your site →About cronlint
cronlint is a zero-dependency command-line tool that lints cron expressions to detect schedule problems such as dates that never fire, jobs that run excessively, and issues related to daylight saving time changes. It can be installed globally via npm or run without installation using npx, and it accepts a single cron expression or input piped from a crontab. The tool provides several output formats, including compact, GitHub annotation, and JSON, and supports options for evaluating daylight saving time rules against specific time zones and for treating warnings as errors in strict mode. It is distributed under the MIT license and was created by René Peter.
- Website
- cronlint.org
- Categories
- Computer software