npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

cron-quartz-validator

v2.1.1

Published

cron quartz expression validator

Downloads

462

Readme

cron-quartz-validator

npm version Test TypeScript license

cron-quartz-validator is a Node.js library (written in TypeScript) to validate Quartz cron expressions.

Installation

npm install cron-quartz-validator

Usage

validateCronExpression takes a string (the cron expression) and returns { valid: boolean, errors: string[] }:

import { validateCronExpression } from "cron-quartz-validator";

validateCronExpression("0 0 12 * * ?");
// { valid: true, errors: [] }

validateCronExpression("* * * * * * *");
// { valid: false, errors: [ ... ] }

validateCronExpression("* * * * 25/2 ? *");
// { valid: false, errors: [ "Month must be between 1 and 12, or JAN-DEC" ] }

isValidCronExpression is a convenience wrapper that just returns the boolean:

import { isValidCronExpression } from "cron-quartz-validator";

if (isValidCronExpression("0 0 12 1/2 * ? *")) {
  // Your code
}

Cron accepted values

Seconds:      0-59       *  ,  -  /
Minutes:      0-59       *  ,  -  /
Hours:        0-23       *  ,  -  /
Day of Month: 1-31       *  ,  -  /  ?  L  LW
Month:        1-12 or JAN-DEC   *  ,  -  /
Day of Week:  1-7  or SUN-SAT   *  ,  -  /  ?  L  #
Year:         1970-2199  *  ,  -  /  (optional 7th field)

Development

pnpm i
pnpm typecheck  # tsc --noEmit
pnpm lint       # eslint .
pnpm test       # vitest run
pnpm build      # tsc -p tsconfig.build.json -> dist/

CI runs typecheck, lint, and the test suite on every push to main and on every pull request (.github/workflows/test.yml). Every push to main also bumps package.json's patch version and commits it back (.github/workflows/bump-version.yml). Publishing to npm happens via .github/workflows/publish.yml, triggered by pushing a v*.*.* tag — the published version is taken from the tag itself (not from package.json), so tagging is what actually decides a release's version. Dependabot keeps dependencies and workflow actions up to date (.github/dependabot.yml).

License

ISC