Undertow
Undertow 2.4.0 clears three CVEs and finally lands long-open HTTP/2 and timeout requests
Comparison · DevOps
Libreswan vs Sanity
A side-by-side editorial comparison of Libreswan and Sanity — release velocity, themes, recent moves, and the top alternatives to consider.
Libreswan vs Sanity: at a glance
What is Libreswan?
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.
What is Sanity?
Sanity is paying down its runtime weight while wiring agents into the content layer.
Two lines of work run in parallel across this window. The platform layer is shedding weight and legacy: @sanity/ui v4.0.0 goes ESM-only, moves heavy components behind subpath imports, and requires a stylesheet import, while the Media Library asset grid switches to viewport-only rendering. The agent layer is filling out fast — two MCP server releases in under a week add CLI execution, explicit release IDs, and transactional document patching, and the React App SDK gains bidirectional presence that interoperates with Studio.
Libreswan vs Sanity: editorial side-by-side
Libreswan
2.5DEVOPS
IPsec daemon shipping back-to-back CVE releases, one of them found by an AI audit.
◆ Current state
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.
◆ Where it's heading
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.
◆ Prediction
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.
Sanity
6.3DEVOPS
Sanity is paying down its runtime weight while wiring agents into the content layer.
◆ Current state
Two lines of work run in parallel across this window. The platform layer is shedding weight and legacy: @sanity/ui v4.0.0 goes ESM-only, moves heavy components behind subpath imports, and requires a stylesheet import, while the Media Library asset grid switches to viewport-only rendering. The agent layer is filling out fast — two MCP server releases in under a week add CLI execution, explicit release IDs, and transactional document patching, and the React App SDK gains bidirectional presence that interoperates with Studio.
◆ Where it's heading
The MCP server is being hardened into a supervised write path rather than a read-only convenience: patches roll back as a unit, malformed IDs are rejected up front, and schema deploys now refuse to touch a Studio-managed workspace even when stale state says otherwise. That last rule is the direction in miniature — agents are being given real write access, fenced off by workspace ownership. Meanwhile the frontend packages are absorbing a breaking release to make bundle size a property of what you import rather than what ships.
◆ Prediction
The v4.0.0 notes state that more components move off runtime CSS-in-JS across the 4.x minors, so the bundle work continues incrementally rather than in another breaking jump. On the SDK side the presence release explicitly defers rendered remote selections to a forthcoming Portable Text plugin — the most concretely signposted next item in the feed.
Alternatives to Libreswan and Sanity
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 Sanity.
Betaflight
Betaflight grew a real autopilot: waypoint missions, geofence RTH and MAVLink ground control
OceanBase
OceanBase is rebuilding itself as a RAG backend without giving up the HTAP story
QGroundControl
QGroundControl rebuilt its flight UI around touch screens, then went quiet for ten months
Pelican
Pelican now ships roughly once a year, and 4.12 is theme housekeeping
WildFly
WildFly's quarterly train is really a stability ladder, and OIDC keeps climbing it
See all Libreswan alternatives → · See all Sanity alternatives →
Recent activity from Libreswan and Sanity
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 17h agoSanityMCP server v2.28.0: Explicit release IDs and safer schema management
- 1d agoSanitySanity UI v4.0.0: Smaller bundles, subpath imports, and a required stylesheet ⚡
- 5d agoSanitySanity Studio v6.9.1: Fixes media library video CORS error and validation fixes
- 5d agoSanityMedia Library: Faster asset grid, and key media library bugfixes
- 6d agoSanityMCP server v2.27.0: Run Sanity CLI commands and safer document patching
- 7d agoSanitySanity Studio v6.9.0: Improve structure tool stability, CLI behavior, and TypeScript schema typings
- 25d agoLibreswan5.3.2 Security Release addresses CVE-2026-14957
- 1mo agoLibreswan5.3.1 Security Release addresses 3 CVEs
- 2y agoLibreswanIKEv1 cryptosuite defaults tightened; systemd libxz dependency dropped
- 2y agoLibreswanCompile error fix carried over from 4.13
Frequently asked questions
What is the difference between Libreswan and Sanity?
They serve adjacent needs but don't currently overlap on shipped themes. Sanity is currently shipping more aggressively (velocity 6.3 vs 2.5), with 1 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.
Is Libreswan better than Sanity?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Sanity is currently shipping more aggressively (velocity 6.3 vs 2.5), with 1 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.
What are the best alternatives to Libreswan?
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.
What are the best alternatives to Sanity?
Top Sanity alternatives in DevOps are ranked by recent ship velocity. Browse the "Sanity alternatives" section above for the current picks, or visit /alternatives/sanity for the full list with editorial commentary on each.