ESPHome
ESPHome 2026.9.0 ships template climate component, OTA encryption with API key, and ESP-NOW for ESP32-P4
A side-by-side editorial comparison of Greenbone Vulnerability Manager and Skipper — release velocity, themes, recent moves, and the top alternatives to consider.
Greenbone GVM adds web application VT scanning and async report export scheduling
Greenbone Vulnerability Manager (gvmd) has shipped four feature releases in roughly six weeks, centering on two themes: web application vulnerability scanning (ZAP VTs loaded into the database as a new 'Web Application VT' subtype) and report export infrastructure (async scheduling, polling, GMP command support). The integration of OWASP ZAP vulnerability tests into GVM's VT database is the most directional change — it extends GVM's scanning coverage beyond network and host vulnerabilities into web application-layer findings.
Skipper adds Redis as a distributed L2 cache backend amid a high-frequency patch cadence.
Skipper is running in a maintenance-heavy patch cycle, shipping multiple versions per week focused on stability, test infrastructure, and minor performance work. The architectural addition this period is v0.27.92's Redis L2 storage for the cache() filter, which extends caching from node-local to cluster-shared. v0.27.95's parsed filter and predicate caching across RouteGroups is a performance improvement but stays within the current architecture.
Greenbone Vulnerability Manager (gvmd) has shipped four feature releases in roughly six weeks, centering on two themes: web application vulnerability scanning (ZAP VTs loaded into the database as a new 'Web Application VT' subtype) and report export infrastructure (async scheduling, polling, GMP command support). The integration of OWASP ZAP vulnerability tests into GVM's VT database is the most directional change — it extends GVM's scanning coverage beyond network and host vulnerabilities into web application-layer findings.
GVM is building toward a more comprehensive vulnerability management platform that covers web applications alongside traditional network targets. The ZAP VT integration (v26.35.0) and the dedicated web_application_vt GMP subtype suggest this is a strategic integration rather than a one-off import. Report export scheduling (v26.37.0–26.38.0) addresses a real operational need for teams that need to push findings to external systems on a schedule rather than on-demand. Agent application severities and OCI image target improvements show the platform expanding into container and agentic workload scanning.
The ZAP VT subtype will gain dedicated reporting and filtering capabilities in the next few releases, since the data model is now in place but the UI and workflow support will need to catch up. OCI image scanning is likely to get more depth given the ongoing container target improvements.
Skipper is running in a maintenance-heavy patch cycle, shipping multiple versions per week focused on stability, test infrastructure, and minor performance work. The architectural addition this period is v0.27.92's Redis L2 storage for the cache() filter, which extends caching from node-local to cluster-shared. v0.27.95's parsed filter and predicate caching across RouteGroups is a performance improvement but stays within the current architecture.
The Redis L2 integration suggests the Skipper team is addressing the multi-replica cache coherence problem that large deployments encounter. If this pattern continues, distributed-state options—persistent rate limiting, distributed circuit breakers using the same Redis client abstraction—are the natural follow-ons. The high patch cadence signals active production deployment rather than feature-driven development.
The Redis client abstraction introduced in v0.27.92 will be extended to other stateful filters, particularly rate limiting, given that distributed rate limiting is the most common request for API gateways running at multi-replica scale.
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 Greenbone Vulnerability Manager or Skipper.
ESPHome 2026.9.0 ships template climate component, OTA encryption with API key, and ESP-NOW for ESP32-P4
Redocly ships a built-in MCP server page across its entire docs platform, with public and authenticated endpoints
Expo kills its AI agent, SDK 58 beta arrives as EAS observability stack hits GA
Jackett in pure tracker-maintenance mode, daily domain and category updates only
Kubernetes v1.37 matures its memory management and scheduling stack for AI/ML workloads.
GitHub Copilot gets cost-aware inference tiers as enterprise AI tooling tightens across the platform.
See all Greenbone Vulnerability Manager alternatives → · See all Skipper 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 7.5 vs 5.0), 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.
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Skipper is currently shipping more aggressively (velocity 7.5 vs 5.0), with 1 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 Greenbone Vulnerability Manager alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Greenbone Vulnerability Manager alternatives" section above for the current picks, or visit /alternatives/greenbone-gvmd for the full list with editorial commentary on each.
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.