ZoneMinder
ZoneMinder 1.38.5 fixes 19 vulnerabilities, including authenticated remote code execution
A side-by-side editorial comparison of Routinator and Terragrunt — release velocity, themes, recent moves, and the top alternatives to consider.
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.
Terragrunt 1.2's last candidate finishes eleven experiments and locks down state buckets.
Terragrunt v1.2.0-rc3, dated mid-October, is declared the final candidate: unless a blocker appears, v1.2.0 ships with its contents. The cycle completes eleven experiments, among them OCI, block-iteration, azure-backend and optional-hooks. Two changes need attention: base64gzip() now returns the Go 1.27 encoder's output, which can trigger resource replacements, and S3 bootstrapping no longer adds the RootAccess bucket policy statement.
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.
Terragrunt v1.2.0-rc3, dated mid-October, is declared the final candidate: unless a blocker appears, v1.2.0 ships with its contents. The cycle completes eleven experiments, among them OCI, block-iteration, azure-backend and optional-hooks. Two changes need attention: base64gzip() now returns the Go 1.27 encoder's output, which can trigger resource replacements, and S3 bootstrapping no longer adds the RootAccess bucket policy statement.
The graduation model has repeated at a larger scale: six experiments in v1.1, eleven in v1.2. The candidates ran as stabilization, with fixes concentrated in the CAS, the catalog and the Provider Cache Server. Each breaking change also ships with an escape hatch, base64gzip_compat() or enable_bucket_root_access, which shows how seriously the project treats its 1.0 guarantees.
v1.2.0 final is the next release, since rc3 says only regression or urgent fixes will land first. It has not appeared in this feed in the 18 days since rc3.
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 Routinator or Terragrunt.
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 Routinator alternatives → · See all Terragrunt alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Routinator and Terragrunt 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. Routinator and Terragrunt 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 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.
Top Terragrunt alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Terragrunt alternatives" section above for the current picks, or visit /alternatives/terragrunt for the full list with editorial commentary on each.