ESPHome
ESPHome ships on a calendar, and the August beta train is already three builds deep.
Comparison · Infra & APIs
Cronicle vs goodpractice
A side-by-side editorial comparison of Cronicle and goodpractice — release velocity, themes, recent moves, and the top alternatives to consider.
Cronicle vs goodpractice: at a glance
What is Cronicle?
The job scheduler's release stream is now almost entirely vulnerability patching and authorization hardening.
Cronicle is a self-hosted distributed job scheduler with a web UI, plugin-defined job types, and a multi-server cluster model. Its 0.9.11x-0.9.12x releases are dominated by two threads: dependency bumps closing published vulnerabilities in sanitize-html, nanoid, shell-quote, ws, and nodemailer, and a sustained authorization review of its own. Version 0.9.125 restored cluster authentication clock validation, aligned job log access checks with job details, moved event filtering server-side, and hardened authorization for event placement and manual run targets; 0.9.124 restricted event and job parameters to those a plugin actually defines.
What is goodpractice?
The R package-quality checker returns from CRAN limbo with checks you can select by category.
goodpractice runs a battery of static checks over an R package — style, complexity, test coverage, documentation, DESCRIPTION hygiene — and reports what a reviewer would flag. The package was archived on CRAN, adopted by rOpenSci in 1.0.5, and version 1.1 is the first substantive release since: every check now belongs to one of 16 named groups, discoverable via all_check_groups() and selectable via checks_by_group(), with group-level exclusion through an option or environment variable and new default_checks() and tidyverse_checks() presets.
Cronicle vs goodpractice: editorial side-by-side
Cronicle
5.0INFRA · APIS
The job scheduler's release stream is now almost entirely vulnerability patching and authorization hardening.
◆ Current state
Cronicle is a self-hosted distributed job scheduler with a web UI, plugin-defined job types, and a multi-server cluster model. Its 0.9.11x-0.9.12x releases are dominated by two threads: dependency bumps closing published vulnerabilities in sanitize-html, nanoid, shell-quote, ws, and nodemailer, and a sustained authorization review of its own. Version 0.9.125 restored cluster authentication clock validation, aligned job log access checks with job details, moved event filtering server-side, and hardened authorization for event placement and manual run targets; 0.9.124 restricted event and job parameters to those a plugin actually defines.
◆ Where it's heading
The pattern in 0.9.124 and 0.9.125 is not incidental fixes but a systematic pass over where the server trusted client input — parameters, filters, targets, and log access were each independently tightened, and password hashing moved from the unmaintained bcrypt-node to bcryptjs in 0.9.123. Feature work is essentially absent from this window; what is not security is dependency maintenance or narrow platform compatibility, like FreeBSD process monitoring in 0.9.126. For a scheduler that executes arbitrary commands across a cluster, that allocation is defensible.
◆ Prediction
Given that each recent release closes another category of over-trusted input, expect the hardening sweep to continue through the remaining API surface before feature work resumes.
goodpractice
0.0INFRA · APIS
The R package-quality checker returns from CRAN limbo with checks you can select by category.
◆ Current state
goodpractice runs a battery of static checks over an R package — style, complexity, test coverage, documentation, DESCRIPTION hygiene — and reports what a reviewer would flag. The package was archived on CRAN, adopted by rOpenSci in 1.0.5, and version 1.1 is the first substantive release since: every check now belongs to one of 16 named groups, discoverable via all_check_groups() and selectable via checks_by_group(), with group-level exclusion through an option or environment variable and new default_checks() and tidyverse_checks() presets.
◆ Where it's heading
The direction is from a monolithic verdict toward a configurable one. Previously the practical choices were run everything or name individual checks; grouping makes partial adoption tractable, which matters because the full battery is opinionated enough that teams either accept all of it or ignore the tool. The tidyverse_checks() preset makes that explicit — the package is acknowledging that its defaults encode one house style among several. Earlier releases pointed the same way with a configurable cyclomatic complexity limit and adjustable output length.
◆ Prediction
With grouping and presets in place, the natural next step is per-project persistent configuration so exclusions live in the repository rather than in an option or environment variable.
Alternatives to Cronicle and goodpractice
Other Infra & APIs products tracked by Sparkpulse, ranked by recent ship velocity. Each card links to a full editorial trajectory and lets you pivot into a head-to-head comparison with either Cronicle or goodpractice.
Helm
Helm runs two release trains in lockstep while v3 walks toward end-of-life.
quarto
Quarto's editor extension is quietly becoming Positron-first while keeping VS Code parity.
q2
Ten releases in six days, methodically porting Quarto's surface into a Rust binary.
pkgcache
The metadata cache under pak now speaks to authenticated and corporate repositories.
packrat
R's old dependency manager now runs on a vendored copy of its own successor.
See all Cronicle alternatives → · See all goodpractice alternatives →
Recent activity from Cronicle and goodpractice
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 22h agoCroniclenanoid vulnerability bump, pixl-server-user to v2
- 1d agoCroniclesanitize-html and nanoid vulnerability fixes
- 8d agoCronicleFreeBSD compatibility for process monitoring
- 14d agoCronicleCluster auth clock validation restored, five authorization gaps closed
- 28d agoCronicleEvent and job parameters restricted to plugin-defined ones
- 1mo agoCroniclePassword hashing moved from bcrypt-node to bcryptjs
- 2mo agogoodpracticeChecks organized into 16 selectable groups with presets ⚡
- 2y agogoodpracticerOpenSci takes over maintenance, package restored to CRAN
- 4y agogoodpracticeConfigurable cyclomatic complexity limit and output length
- 5y agogoodpracticePackage logo added
Frequently asked questions
What is the difference between Cronicle and goodpractice?
They serve adjacent needs but don't currently overlap on shipped themes. Cronicle is currently shipping more aggressively (velocity 5.0 vs 0.0), with 0 editorial sparks in the last 30 days against 0. See the at-a-glance table above for a side-by-side breakdown of velocity, recent sparks, and editorial themes.
Is Cronicle better than goodpractice?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Cronicle is currently shipping more aggressively (velocity 5.0 vs 0.0), with 0 editorial sparks in the last 30 days against 0. For your specific use case, the alternatives sections above list other Infra & APIs products to evaluate alongside.
What are the best alternatives to Cronicle?
Top Cronicle alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Cronicle alternatives" section above for the current picks, or visit /alternatives/cronicle for the full list with editorial commentary on each.
What are the best alternatives to goodpractice?
Top goodpractice alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "goodpractice alternatives" section above for the current picks, or visit /alternatives/goodpractice for the full list with editorial commentary on each.