Undertow
Undertow 2.4.0 clears three CVEs and finally lands long-open HTTP/2 and timeout requests
A side-by-side editorial comparison of Libreswan and SimpleSAMLphp — release velocity, themes, recent moves, and the top alternatives to consider.
IPsec daemon shipping back-to-back CVE releases, one of them found by an AI audit.
Libreswan is an IKE/IPsec implementation, and its recent visible releases are entirely security-driven: 5.3.1 addressed three CVEs, and 5.3.2 followed a month later with a single one. The 5.3.2 note discloses that the project ran an AI-assisted audit of its own codebase, which surfaced an assertion failure reachable through a malformed X.509 certificate in FIPS mode. The older entries in this feed are raw commit-log dumps from the 4.x and 5.0rc era rather than curated notes.
Two maintenance branches, patched in lockstep, with release notes that say nothing but a checksum.
SimpleSAMLphp is running parallel 2.4 and 2.5 maintenance branches and patching both on the same day whenever a fix lands. The August releases are a coordinated security drop across the 2.5 line plus a 2.4 bugfix a day earlier. Release bodies carry no changelog text at all — just a download link, upgrade-notes pointer, and SHA256 checksums, so the feed tells operators when to patch but never what changed.
Libreswan is an IKE/IPsec implementation, and its recent visible releases are entirely security-driven: 5.3.1 addressed three CVEs, and 5.3.2 followed a month later with a single one. The 5.3.2 note discloses that the project ran an AI-assisted audit of its own codebase, which surfaced an assertion failure reachable through a malformed X.509 certificate in FIPS mode. The older entries in this feed are raw commit-log dumps from the 4.x and 5.0rc era rather than curated notes.
The project is auditing itself more aggressively than its release cadence suggests, and the parsing paths — certificate handling, IKEv1 proposal defaults — are where the findings keep landing. The 5.0 work visible here was a deliberate tightening of IKEv1 cryptosuite defaults, and the current CVE stream is the same instinct applied to inputs an attacker controls.
Further findings from the same audit path would surface as additional point releases against certificate and packet parsing; the entries do not indicate whether the audit is complete.
SimpleSAMLphp is running parallel 2.4 and 2.5 maintenance branches and patching both on the same day whenever a fix lands. The August releases are a coordinated security drop across the 2.5 line plus a 2.4 bugfix a day earlier. Release bodies carry no changelog text at all — just a download link, upgrade-notes pointer, and SHA256 checksums, so the feed tells operators when to patch but never what changed.
This is pure maintenance cadence, not product development. The pattern across the last ten releases is consistent: security issues get simultaneous twin tags on both supported branches, everything else lands as branch-local bugfix points. The only release in the window that documented its own content was v2.4.6/v2.5.1 in May, which listed three GHSA advisories.
Expect the next tags to continue the twin-branch pattern — a paired 2.4.x and 2.5.x whenever an advisory lands, with content again deferred to the external changelog.
Other DevOps 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 Libreswan or SimpleSAMLphp.
Undertow 2.4.0 clears three CVEs and finally lands long-open HTTP/2 and timeout requests
Betaflight grew a real autopilot: waypoint missions, geofence RTH and MAVLink ground control
OceanBase is rebuilding itself as a RAG backend without giving up the HTAP story
QGroundControl rebuilt its flight UI around touch screens, then went quiet for ten months
Pelican now ships roughly once a year, and 4.12 is theme housekeeping
WildFly's quarterly train is really a stability ladder, and OIDC keeps climbing it
See all Libreswan alternatives → · See all SimpleSAMLphp alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. SimpleSAMLphp 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. SimpleSAMLphp 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 DevOps products to evaluate alongside.
Top Libreswan alternatives in DevOps are ranked by recent ship velocity. Browse the "Libreswan alternatives" section above for the current picks, or visit /alternatives/libreswan for the full list with editorial commentary on each.
Top SimpleSAMLphp alternatives in DevOps are ranked by recent ship velocity. Browse the "SimpleSAMLphp alternatives" section above for the current picks, or visit /alternatives/simplesamlphp for the full list with editorial commentary on each.