Pressable
Ten days of bulk operations, then the AI assistant got the keys to multi-site access control.
A side-by-side editorial comparison of Skipper and Jackett — release velocity, themes, recent moves, and the top alternatives to consider.
One pull request per version tag, and most of them are dependency bumps.
Skipper cuts a release for essentially every merged pull request — six tags between 27 July and 7 August, each containing a single change. Two of the six are Dependabot bumps to CI actions and a fuzzing base image, two are test-only adjustments, and one fixes an error type assertion. Every entry carries the same boilerplate pointing at the multiarch image in GitHub's registry.
A daily indexer-repair treadmill: Jackett patches tracker definitions as fast as trackers change.
Jackett cuts a release nearly every morning, and each one is a batch of tracker-definition edits rather than application changes. Across the last ten releases there is no work on Jackett itself — no UI, no API, no core engine changes — only YAML definitions: domain bumps, category mappings, selector repairs, auth-format switches, and removals of trackers that went dark. The one direction of growth is the catalog: simurg was added as a new private tracker, while desigaane and simurg both moved to API-key authentication for downloads.
Skipper cuts a release for essentially every merged pull request — six tags between 27 July and 7 August, each containing a single change. Two of the six are Dependabot bumps to CI actions and a fuzzing base image, two are test-only adjustments, and one fixes an error type assertion. Every entry carries the same boilerplate pointing at the multiarch image in GitHub's registry.
The visible work is maintenance of an already-stable proxy rather than feature development. What the test changes hint at is where the correctness concerns sit: an OPA policy test updated to explicitly deny truncated request bodies, because oversized JSON cannot be fully parsed and a policy that ignores input.truncated_body can be bypassed. That is authorization-under-load hardening, and it is the most interesting thing in the window even though it landed as a test.
The per-PR tagging rhythm will continue producing several versions a week regardless of change size. Readers tracking this product should expect the meaningful changes to be a small minority of the tags.
Jackett cuts a release nearly every morning, and each one is a batch of tracker-definition edits rather than application changes. Across the last ten releases there is no work on Jackett itself — no UI, no API, no core engine changes — only YAML definitions: domain bumps, category mappings, selector repairs, auth-format switches, and removals of trackers that went dark. The one direction of growth is the catalog: simurg was added as a new private tracker, while desigaane and simurg both moved to API-key authentication for downloads.
This is maintenance mode by design, not by neglect. The work is reactive on a one-day lag: a tracker moves hosts or changes markup, and the definition follows in the next morning's release. Volume holds steady at roughly three to eight commits per release with no accumulation toward a larger change, and the removals (FilmesHdTorrent, torr9, rain) roughly offset the additions.
Expect the same daily cadence of definition patches — more domain bumps, more category mappings, and further migrations to API-key auth as trackers close off unauthenticated scraping. Nothing in these entries points to core application work being queued.
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 Skipper or Jackett.
Ten days of bulk operations, then the AI assistant got the keys to multi-site access control.
A v5 release candidate train carrying a database migrator that has to work on the first try.
The syslog daemon is quietly becoming an OpenTelemetry-era pipeline, YAML config and all.
Three supported branches, patched in lockstep within the same minute.
The changelog is a raw commit log, and its severity tags tell you more than the prose would.
The eBPF observability tool just started reaching for the GPU.
See all Skipper alternatives → · See all Jackett alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
Both compete on the same themes — maintenance — within Infra & APIs. Skipper 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.
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Skipper 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.
Top Skipper alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Skipper alternatives" section above for the current picks, or visit /alternatives/skipper for the full list with editorial commentary on each.
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.