ESPHome
ESPHome ships on a calendar, and the August beta train is already three builds deep.
Comparison · Infra & APIs
Helm vs Jackett
A side-by-side editorial comparison of Helm and Jackett — release velocity, themes, recent moves, and the top alternatives to consider.
Helm vs Jackett: at a glance
What is Helm?
Helm runs two release trains in lockstep while v3 walks toward end-of-life.
Helm ships v4 and v3 in paired patch releases, usually minutes apart, with v3 explicitly flagged as approaching end-of-life since v3.21.0. The August patches split along that line: v4.2.4 carries functional fixes — error reporting for helm template --debug --show-only, logs collected from all containers in test pods, a panic on repeated IsReachable calls, missing conflict retry under server-side apply, and registry push token scoping — while v3.21.4 is almost entirely backported dependency bumps closing Go vulnerability advisories. Several releases in this window carry no notable changes at all beyond platform checksums.
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.
Helm vs Jackett: editorial side-by-side
Helm
5.0INFRA · APIS
Helm runs two release trains in lockstep while v3 walks toward end-of-life.
◆ Current state
Helm ships v4 and v3 in paired patch releases, usually minutes apart, with v3 explicitly flagged as approaching end-of-life since v3.21.0. The August patches split along that line: v4.2.4 carries functional fixes — error reporting for helm template --debug --show-only, logs collected from all containers in test pods, a panic on repeated IsReachable calls, missing conflict retry under server-side apply, and registry push token scoping — while v3.21.4 is almost entirely backported dependency bumps closing Go vulnerability advisories. Several releases in this window carry no notable changes at all beyond platform checksums.
◆ Where it's heading
The two branches are diverging in kind rather than in version number. New behavior lands on v4; v3 receives security backports and Kubernetes client library alignment, which is what a maintenance branch looks like before it is retired. Within v4, the recurring theme is concurrency and lifecycle correctness — data races between upgrade and rollback, a WaitForDelete watch cancelled too early, a race fix reverted in v4.2.2 and revisited later — suggesting the v4 rewrite surfaced timing behavior the v3 code path never exercised.
◆ Prediction
Expect the v3 line to narrow to security backports only until its end-of-life date lands, with functional work continuing exclusively on the v4.2.x patch series.
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 Helm 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 Helm or Jackett.
Cronicle
The job scheduler's release stream is now almost entirely vulnerability patching and authorization hardening.
goodpractice
The R package-quality checker returns from CRAN limbo with checks you can select by category.
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 Helm alternatives → · See all Jackett alternatives →
Recent activity from Helm and Jackett
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 2h agoHelmv4 patch: template debugging, test pod logs, apply conflict retry
- 2h agoHelmv3 patch: four Go vulnerability advisories closed via backports
- 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
- 1mo agoHelmHelm v3.21.3
- 1mo agoHelmHelm v4.2.3
- 1mo agoHelmv3 client libraries aligned to Kubernetes v1.36
- 1mo agoHelmv4 patch reverting a WaitForDelete race fix
Frequently asked questions
What is the difference between Helm and Jackett?
They serve adjacent needs but don't currently overlap on shipped themes. Helm and Jackett are shipping at a similar cadence (velocity 5.0 vs 5.0, both within Sparkpulse's "active" band). See the at-a-glance table above for a side-by-side breakdown of velocity, recent sparks, and editorial themes.
Is Helm better than Jackett?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Helm and Jackett are shipping at a similar cadence (velocity 5.0 vs 5.0, both within Sparkpulse's "active" band). For your specific use case, the alternatives sections above list other Infra & APIs products to evaluate alongside.
What are the best alternatives to Helm?
Top Helm alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Helm alternatives" section above for the current picks, or visit /alternatives/helm 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.