Casdoor
Casdoor tags a release almost daily, and nearly all of it is multi-tenant boundary repair.
A side-by-side editorial comparison of Jackett and quarto-r — release velocity, themes, recent moves, and the top alternatives to consider.
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.
The R side of Quarto stopped being a render wrapper and became a project interface
The quarto R package gives R users programmatic access to the Quarto CLI, and its 1.4 release is where that access stopped being a thin call to quarto render. Project creation, extension installation, template use, environment diagnostics and a vignette engine all arrived together, and 1.5.0 followed by changing how output paths are communicated to the CLI — through Quarto metadata rather than a command-line flag.
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.
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.
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.
The quarto R package gives R users programmatic access to the Quarto CLI, and its 1.4 release is where that access stopped being a thin call to quarto render. Project creation, extension installation, template use, environment diagnostics and a vignette engine all arrived together, and 1.5.0 followed by changing how output paths are communicated to the CLI — through Quarto metadata rather than a command-line flag.
The package's job is to stay a faithful surface over a CLI it does not control, and the releases show what that costs. Version numbers track the Quarto release they target, tests are adapted around upstream regressions, and behaviour is reworked when the CLI changes — quarto_use_template() now errors clearly in non-empty directories because interactive prompting was never suitable for programmatic use. The 1.5.1 release exists entirely so CRAN checks pass on machines where Quarto is not installed at all.
Expect the next release to track the next Quarto CLI version, with the open question in the feed being how --no-prompt behaviour settles upstream for template use. Feature work here follows the CLI rather than leading it.
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 Jackett or quarto-r.
Casdoor tags a release almost daily, and nearly all of it is multi-tenant boundary repair.
A stable WebSocket client for R whose recent releases are almost entirely toolchain survival.
ESPHome ships on a calendar, and the August beta train is already three builds deep.
The job scheduler's release stream is now almost entirely vulnerability patching and authorization hardening.
Helm runs two release trains in lockstep while v3 walks toward end-of-life.
The R package-quality checker returns from CRAN limbo with checks you can select by category.
See all Jackett alternatives → · See all quarto-r alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
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.
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.
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.
Top quarto-r alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "quarto-r alternatives" section above for the current picks, or visit /alternatives/quarto-r for the full list with editorial commentary on each.