Jackett
Daily tags chasing tracker domain moves, login changes and freeleech detection
A side-by-side editorial comparison of FOSSA CLI and Skipper — release velocity, themes, recent moves, and the top alternatives to consider.
Ecosystem-by-ecosystem parser coverage is the whole roadmap.
fossa-cli releases every one to two weeks, and nearly every change is about correctly reading one more package manager's metadata. In this window alone: pnpm lockfile handling refactored, npm v3 lockfiles taught target-level dependency scoping, Node workspaces matched when declared with a leading ./, sbt 1.4+ routed through DependencyTreePlugin, Conan list-valued licenses handled, and container scanning extended to /var/lib/dpkg/status.d.
Skipper trims a 4x memory regression out of routesrv, days after shipping h2c
Zalando's HTTP router ships patch tags almost daily, and most carry a single dependency bump or a one-line auth fix. The substance in this window is v0.27.63, which stops routesrv holding an uncompressed route tree alongside the compressed buffer: retained memory in the release's own benchmark falls from 30.7 MB to 2.0 MB, undoing most of the 4x increase zone-aware routing had introduced. Around it sit narrow auth repairs, and an eskip parser change that finally accepts negative numeric arguments in predicates and filters.
fossa-cli releases every one to two weeks, and nearly every change is about correctly reading one more package manager's metadata. In this window alone: pnpm lockfile handling refactored, npm v3 lockfiles taught target-level dependency scoping, Node workspaces matched when declared with a leading ./, sbt 1.4+ routed through DependencyTreePlugin, Conan list-valued licenses handled, and container scanning extended to /var/lib/dpkg/status.d.
This is the unglamorous core of dependency scanning: correctness depends on parsing every ecosystem's format exactly, and every ecosystem keeps changing its format. The work arrives as many small, ticket-tracked strategy fixes rather than architectural change, and it comes from a mix of regular maintainers and first-time contributors. Some releases exist only to cut a version.
Expect the same cadence of per-ecosystem parser fixes to continue, since that is what every release in this window consists of; nothing in the entries points to a structural change in how strategies are implemented.
Zalando's HTTP router ships patch tags almost daily, and most carry a single dependency bump or a one-line auth fix. The substance in this window is v0.27.63, which stops routesrv holding an uncompressed route tree alongside the compressed buffer: retained memory in the release's own benchmark falls from 30.7 MB to 2.0 MB, undoing most of the 4x increase zone-aware routing had introduced. Around it sit narrow auth repairs, and an eskip parser change that finally accepts negative numeric arguments in predicates and filters.
Two threads run through the recent tags. The data path keeps getting real work - leastRequests balancing, then h2c end to end in v0.27.57, now the memory cost of zone-aware routing being paid back. The auth filters, by contrast, are only being maintained: token introspection, grant auth, and now the OIDC Referer handling are fixes rather than new capability, and several are follow-ups to each other rather than independent bugs.
Zone-aware routing looks like the source of the recent memory attention, so expect further tuning around route storage and the hash computation done on every pull, which the release's second benchmark already isolates. The OIDC cookie change is the second link in an auth chain that started with the grant-auth fix, and is likely to draw another follow-up.
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 FOSSA CLI or Skipper.
Daily tags chasing tracker domain moves, login changes and freeleech detection
CloudStack ships two LTS branches in lockstep and publishes nothing but pointers
Kinsta is moving MyKinsta's controls into its API, one surface per month
Verdaccio's 7.0 line is subtraction — forks dropped, toolchain swapped, tags mostly empty
Observability lands on OpenTelemetry semconv in the LTS train
Canvas agents gain memory, and onboarding moves into the editor
See all FOSSA CLI alternatives → · See all Skipper alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. FOSSA CLI and Skipper 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. FOSSA CLI and Skipper 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 FOSSA CLI alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "FOSSA CLI alternatives" section above for the current picks, or visit /alternatives/fossa-cli for the full list with editorial commentary on each.
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.