ESPHome
ESPHome ships on a calendar, and the August beta train is already three builds deep.
Comparison · Infra & APIs
goodpractice vs Jackett
A side-by-side editorial comparison of goodpractice and Jackett — release velocity, themes, recent moves, and the top alternatives to consider.
goodpractice vs Jackett: at a glance
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.
What is Jackett?
A daily auto-generated build stream where every release is tracker definitions and nothing else.
Jackett ships a build most mornings, each one an auto-generated list of commits against individual tracker definitions. The current window is entirely that: docspedia switching to cookie authentication with new selectors, nyaa season-title search taking episode info into account, a cardigann fix that stops duplicate GET requests, and a run of domain bumps across magnetcat, torrenttip, torrentsome, 52bt and hd-club. One tracker, 720pier, was removed against an open issue. Nothing in the window touches the application itself.
goodpractice vs Jackett: editorial side-by-side
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.
Jackett
5.0INFRA · APIS
A daily auto-generated build stream where every release is tracker definitions and nothing else.
◆ Current state
Jackett ships a build most mornings, each one an auto-generated list of commits against individual tracker definitions. The current window is entirely that: docspedia switching to cookie authentication with new selectors, nyaa season-title search taking episode info into account, a cardigann fix that stops duplicate GET requests, and a run of domain bumps across magnetcat, torrenttip, torrentsome, 52bt and hd-club. One tracker, 720pier, was removed against an open issue. Nothing in the window touches the application itself.
◆ Where it's heading
The project's work is catalogue maintenance, and the release notes are a ledger of the indexer ecosystem decaying and being repaired — domains rotate, selectors break, sites disappear, and each is patched within a day. The cardigann duplicate-request fix is the rare item that touches shared scraping machinery rather than one site's definition. Cadence is high and consistent, but throughput here measures upkeep, not development.
◆ Prediction
Expect the same daily definition builds: domain rotations, selector repairs, and occasional additions and removals as trackers appear and fold. Anything at the application level would have to show up outside this auto-generated stream, and these entries give no sign of it.
Alternatives to goodpractice and Jackett
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 goodpractice or Jackett.
Cronicle
The job scheduler's release stream is now almost entirely vulnerability patching and authorization hardening.
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.
See all goodpractice alternatives → · See all Jackett alternatives →
Recent activity from goodpractice and Jackett
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 11h agoJackettdocspedia cookie auth, nyaa season search, duplicate GET fix
- 1d agoJackettDomain bumps across five trackers; 720pier removed
- 2d agoJackettScenetime indexer added; kunlun and MTV trackers removed
- 3d agoJackettTimezone fix, request delay and an anime category across four trackers
- 4d agoJackettNew domains for several trackers plus a public DHT crawler
- 5d agoJackettOne tracker removed, selectors and alternate domains corrected
- 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 goodpractice and Jackett?
They serve adjacent needs but don't currently overlap on shipped themes. Jackett 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 goodpractice better than Jackett?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Jackett 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 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.
What are the best alternatives to Jackett?
Top Jackett alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Jackett alternatives" section above for the current picks, or visit /alternatives/jackett for the full list with editorial commentary on each.