ZoneMinder
ZoneMinder 1.38.5 fixes 19 vulnerabilities, including authenticated remote code execution
A side-by-side editorial comparison of Bugsnag and Routinator — release velocity, themes, recent moves, and the top alternatives to consider.
| Feature | Bugsnag | Routinator |
|---|---|---|
| Sector | Infra & APIs | Infra & APIs |
| Velocity score | 2.5 | 5.0 |
| Sparks · 30d | 0 | 0 |
| Top themes | error-tracking, correlated-events, mcp, mobile-monitoring | rpki, aspa, bgp-security, network-infrastructure |
| Last editorial update | 10h ago | 57m ago |
| Website | — | Visit → |
Bugsnag names GraphQL operations and lets iOS teams attach context to app hangs.
September's release is narrow and practical. The iOS SDK's new appHangCallback adds diagnostic context the moment a hang is detected, aimed at SwiftUI hangs where the stack trace alone doesn't show the cause, and GraphQL requests now appear by operation in Network performance views rather than under a single POST /graphql. It follows source-side discard enforcement in August and the Correlated Events work earlier in the year.
Routinator 0.16 will validate ASPA and BGPsec, and run strict, by default
Routinator is a mature RPKI validator with a slow, release-candidate-gated cadence. After a run of security work, including an external audit's four CVEs in 0.15.2 and resource-exhaustion fixes in 0.15.3, 0.16.0-rc1 changes defaults: ASPA and BGPsec are on, strict validation is on, and the old enable flags become --disable-aspa, --disable-bgpsec and --relaxed. It also adds Resource Signed Checklists (RFC 9323), SLURM v2 with ASPA filtering, and a new repository logging scheme that changes the /status JSON.
September's release is narrow and practical. The iOS SDK's new appHangCallback adds diagnostic context the moment a hang is detected, aimed at SwiftUI hangs where the stack trace alone doesn't show the cause, and GraphQL requests now appear by operation in Network performance views rather than under a single POST /graphql. It follows source-side discard enforcement in August and the Correlated Events work earlier in the year.
Bugsnag is moving from single-service error tracking toward cross-service observability: Correlated Events, trace correlation, and the MCP server all point at workflows where an error in one service is causally linked to events in others. The Flutter SDK parity work (CPU, memory, rendering metrics) reflects a deliberate effort to close the feature gap between mobile and web monitoring. SDK Source-Side Discard Enforcement (remote rule push to SDK) reduces bandwidth and processing overhead at scale — a signal that larger enterprise deployments are a growth priority.
Correlated Events will likely expand to support more correlation dimensions — custom attributes, error clusters — and the MCP server toolset will grow to include mutation tools (creating alerts, snoozing errors) rather than just read-only access. The Performance Score metric will gain more visibility and dashboard integrations.
Routinator is a mature RPKI validator with a slow, release-candidate-gated cadence. After a run of security work, including an external audit's four CVEs in 0.15.2 and resource-exhaustion fixes in 0.15.3, 0.16.0-rc1 changes defaults: ASPA and BGPsec are on, strict validation is on, and the old enable flags become --disable-aspa, --disable-bgpsec and --relaxed. It also adds Resource Signed Checklists (RFC 9323), SLURM v2 with ASPA filtering, and a new repository logging scheme that changes the /status JSON.
Having spent 2026 hardening the validator, the maintainers are now changing what operators get out of the box. Defaults moving toward ASPA and strictness put newer RPKI object types on equal footing with route origin validation.
A final 0.16.0 following one or more release candidates is the likely next step, as with 0.15.0.
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 Bugsnag or Routinator.
ZoneMinder 1.38.5 fixes 19 vulnerabilities, including authenticated remote code execution
CRI-O ships patch releases across three branches with empty change notes
Certbot keeps tidying correctness bugs around renewals and hooks
Buildkite drops long-lived GitHub credentials from self-hosted agents
AIReiter adds ByteDance's Seedream 5.0 Flash for fast, low-cost image generation and editing
Dashy shipped ten releases in five days; one fixes how auth headers trust origins
See all Bugsnag alternatives → · See all Routinator alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Routinator is currently shipping more aggressively (velocity 5.0 vs 2.5), 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. Routinator is currently shipping more aggressively (velocity 5.0 vs 2.5), 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 Bugsnag alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Bugsnag alternatives" section above for the current picks, or visit /alternatives/bugsnag for the full list with editorial commentary on each.
Top Routinator alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Routinator alternatives" section above for the current picks, or visit /alternatives/routinator for the full list with editorial commentary on each.