Our take
Quietno commits in the last 90 days- Activity
- 46
- Community
- 38
- Issues
- 35
- Pull requests
- 67
+8 stars in the last 30 days
- Releases more often than 75% of the projects we track
- Slower to close issues than 87% of the projects we track
Croner is a capable, broadly portable cron library with a quiet recent commit history and development concentrated in one maintainer, despite ongoing releases and merged pull requests.
Good fit if
- You need cron scheduling or run-time calculations in JavaScript or TypeScript across Node.js, Deno, Bun, or browsers.
- You want time-zone support, advanced calendar expressions, and job controls without dependencies or an external scheduler.
- An MIT-licensed, in-memory library fits your application, and you can account for its maintainer concentration.
Look elsewhere if
- Your jobs need persistence across process restarts or scheduling backed by a database, which Croner's in-memory design does not provide.
- You require a project with recent commits: the health data reports no commits in the last 90 days, even though releases and pull requests continued during that period.
- Your deployment cannot use the supported JavaScript runtimes or browser builds.
All health signals
| Last commit | 2026-10-13 (2 days ago) |
|---|---|
| Commits, last 90 days | 0 |
| Releases, last 12 months | 21 (latest 11.0.0-dev.4, 2026-10-13, pre-release) |
| Contributors | 20 (top contributor: 88% of commits) |
| Issues closed, last 90 days | 3 (typically closed in 136 days) |
| Pull requests merged, last 90 days | 19 (typically merged in 0 days) |
| Project age | 10 years |
Checked on 2026-10-16 with the GitHub API.
Project history
Daily GitHub snapshots since Oct 7, 2026. History covers stars and forks; health signals are not tracked historically.
Stars
2,617Forks
80Change since Nov 15, 2026: +1 stars·0 forks
Overview
Croner is a zero-dependency JavaScript and TypeScript library built around Vixie Cron expressions. It helps developers schedule functions or inspect when cron patterns will run, with support for Node.js, Deno, Bun, and browsers.
It suits applications that need in-memory scheduling without a separate service or database. Alongside standard cron patterns, it adds calendar modifiers, time-zone support, controls for scheduled jobs, and ways to handle overlapping or failing tasks. See the documentation and GitHub repository for details.
Key Features
- Schedule synchronous or asynchronous functions using cron expressions, dates, or ISO 8601 times.
- Calculate upcoming and previous run times, check whether dates match a pattern, and find the time until the next run.
- Support optional seconds and year fields, plus
L,W,#, and+calendar and logic modifiers. - Schedule against a named time zone, with documented handling of daylight-saving gaps and overlaps.
- Pause, resume, trigger, or stop jobs, and limit runs or minimum time between triggers.
- Configure error handling and overrun protection for scheduled functions.
- Run across Node.js, Deno, Bun, and browser environments, with TypeScript typings and no dependencies.
Use Cases
- A Node.js service can run recurring maintenance tasks without adding a separate scheduler service.
- A browser-based tool can preview upcoming dates for a cron expression or trigger a client-side task.
- A TypeScript application can schedule jobs in a named time zone, such as a daily task tied to a regional business day.
- A developer migrating from another JavaScript cron library can use Croner's extended expression support and job controls, while checking the project's migration guide for behavioral differences.
What you need
Detected in the repository
- TypeScript (main language on GitHub)
- A test suite and automated checks on GitHub Actions
License in plain words
MITpermissive
- Commercial use: yes
- Modify and redistribute: yes
- You must keep: the copyright and license notice
- Share your changes: no
A summary, not legal advice: the LICENSE file is what applies.
Getting Started
Install from npm:
npm install croner
Then import Cron from croner. See the README for usage, runtime-specific installation options, and migration guidance.
Considerations
- The health data labels the project quiet because there were no commits in the last 90 days. It also records releases and merged pull requests during that period, so the quiet status describes commit activity rather than a lack of all project activity.
- The project has 20 contributors, but most contributions are concentrated in one person. Teams adopting it should consider that maintainer concentration when planning long-term support.
- Jobs run in memory, not in a database. A process restart does not provide persistent job state or a durable queue.
- Runtime support has stated minimum versions: Node.js 18, Deno 2, and Bun 1. Unreferenced timers are not supported in browsers.
- The README documents cron extensions and time-zone behavior that may differ from other cron implementations. Validate patterns and migration behavior against your existing scheduler.
- The MIT license permits broad reuse subject to its license terms.
Found this useful?
Share it with someone who would like croner.