gpkg
An R interface to GeoPackage that keeps sanding down its own API
A side-by-side editorial comparison of Jackett and ore — release velocity, themes, recent moves, and the top alternatives to consider.
Jackett's daily release treadmill now spends commits undoing tracker removals it made days earlier.
Jackett ships near-daily auto-generated releases, each carrying a handful of tracker-definition commits: domain bumps, indexers added or removed, request delays, category tweaks. The work is entirely definition maintenance against sites that keep moving — no changes to the application itself appear in this window. Bodies are machine-generated commit lists with no prose.
A stable Oniguruma binding for R that ships correctness fixes and little else.
ore wraps the Oniguruma regex engine for R, and its recent history is entirely about making that binding safe rather than richer. The last three releases fix an infinite-loop hazard on zero-length matches, a named-group propagation bug, and locale detection at startup. The user-facing API has not moved since 1.7.1, when ore_file() began recording whether a file was read as binary.
Jackett ships near-daily auto-generated releases, each carrying a handful of tracker-definition commits: domain bumps, indexers added or removed, request delays, category tweaks. The work is entirely definition maintenance against sites that keep moving — no changes to the application itself appear in this window. Bodies are machine-generated commit lists with no prose.
The notable pattern is reversal. 720pier was removed in v0.24.2404 and restored by revert in v0.24.2414 three days later; scenetime was added as an indexer in v0.24.2398 and dropped four days after in v0.24.2413 when an API class requirement was lifted. Round-trips like these are now a routine part of the cadence, which suggests removals are being made on incomplete information and walked back once users object.
The daily cadence continues, dominated by domain bumps and FlareSolverr dependency updates. Expect further add-then-remove round-trips as tracker sites change their access rules faster than definitions can settle.
ore wraps the Oniguruma regex engine for R, and its recent history is entirely about making that binding safe rather than richer. The last three releases fix an infinite-loop hazard on zero-length matches, a named-group propagation bug, and locale detection at startup. The user-facing API has not moved since 1.7.1, when ore_file() began recording whether a file was read as binary.
This is a package in maintenance, not development. The changes cluster around C-level hygiene — memory leaks, buffer overruns, sprintf() removal, compiler warnings — which reads as keeping CRAN checks green rather than pursuing new capability. Releases arrive in pairs separated by minutes or in gaps of two years, a cadence typical of a package touched only when something breaks or a CRAN policy shifts.
The next release is most likely another correctness or toolchain fix rather than new regex functionality; the README's note about CRAN and mainline diverging suggests the two versions may be reconciled at some point, though the entries do not say when.
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 ore.
An R interface to GeoPackage that keeps sanding down its own API
R's logging package handed to new maintainers and rebuilt from the inside out
Four dormant years end with a test fix, not a feature
Four years of releases land in four minutes as the changelog gets backfilled to GitHub
A comorbidity-coding package relicenses to BSD and grows past the American coding systems
Dragonfly spends its releases on correctness in the parts of Redis compatibility nobody tests.
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 ore alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "ore alternatives" section above for the current picks, or visit /alternatives/ore for the full list with editorial commentary on each.