Aviator
Aviator moves from merging code to judging it: Verify checks PRs against their stated intent.
A side-by-side editorial comparison of Skipper and Woodpecker CI — release velocity, themes, recent moves, and the top alternatives to consider.
Skipper patches its second filter advisory in a week, this one in the OPA request-body filter.
Skipper keeps tagging one release per merge. v0.28.46 fixes advisory GHSA-j3r3-rjcc-vh4q in the opaAuthorizeRequestWithBody filter, reported by an outside researcher, a week after the cache() advisory fix. Between them came v0.28.40's priority routes for binary users, raw-path predicates, and fixes for a JWT cache leak, a headerToQuery bug and an AWS signer data race; v0.28.45 only repairs CI test targets.
Woodpecker CI hardens agent security and forge handling through its 3.14 release candidates
Woodpecker is iterating through 3.14.0 release candidates focused on security and agent/forge robustness: sanitizing agent-introduced state changes and log streaming, blocking registration as arbitrary agents, restricting log access, and cleaning up the Forge interface. Dependency security bumps (axios, otel, follow-redirects) and a lodash removal run throughout.
Skipper keeps tagging one release per merge. v0.28.46 fixes advisory GHSA-j3r3-rjcc-vh4q in the opaAuthorizeRequestWithBody filter, reported by an outside researcher, a week after the cache() advisory fix. Between them came v0.28.40's priority routes for binary users, raw-path predicates, and fixes for a JWT cache leak, a headerToQuery bug and an AWS signer data race; v0.28.45 only repairs CI test targets.
Security hardening at the routing layer is the main thread: outside researchers are reporting filter-level advisories, and the maintainers are answering with fixes plus tools like priority routes that let operators block suspicious paths before any backend sees them. Around that, correctness fixes for concurrency and lifecycle bugs keep landing one tag at a time, and CI coverage is being repaired so race tests actually run.
Expect more advisory fixes in filters that inspect request bodies or paths, and more single-fix tags. The entries don't say whether the advisory details will be published with them.
Woodpecker is iterating through 3.14.0 release candidates focused on security and agent/forge robustness: sanitizing agent-introduced state changes and log streaming, blocking registration as arbitrary agents, restricting log access, and cleaning up the Forge interface. Dependency security bumps (axios, otel, follow-redirects) and a lodash removal run throughout.
The 3.14 line reads as a security-and-internals hardening cycle, tightening the agent trust boundary and forge integration rather than pushing features. The earlier 3.11 line shows the more typical mix of per-repo config features and fixes.
Expect 3.14.0 to converge to a stable release after the RC series, continuing the agent-security and forge-handling focus.
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 Woodpecker CI.
Aviator moves from merging code to judging it: Verify checks PRs against their stated intent.
Infisical stores PAM session recordings in S3 and backs internal CAs with AWS KMS keys.
Airflow 3.4.0 reaches its second beta a day after the common-ai provider hit 1.0.
ESPHome adds a sixth 2026.10 beta, one more than 2026.9 needed before its .0.
Semgrep adds Objective-C as an alpha target, its first new language since Dart went GA.
Currents opens every project on a health verdict: trend, state, and what to fix first.
See all Skipper alternatives → · See all Woodpecker CI alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Skipper 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. Skipper 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 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 Woodpecker CI alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Woodpecker CI alternatives" section above for the current picks, or visit /alternatives/woodpecker-ci for the full list with editorial commentary on each.