Redocly
Redocly ships a built-in MCP server page across its entire docs platform, with public and authenticated endpoints
A side-by-side editorial comparison of Semgrep and ESPHome — release velocity, themes, recent moves, and the top alternatives to consider.
Semgrep extends supply chain coverage to Bazel and squashes a cluster of engine reliability bugs.
Semgrep is shipping weekly releases at a steady pace, advancing on two fronts: broader language and build-system coverage (Bazel/Maven via rules_jvm_external, OpenTofu, Solidity, Ruby parser improvements) and engine reliability (OCaml GC bug fixes, proxy handling, UTF-8 in MCP mode, better crash diagnostics). The Bazel supply chain milestone in v1.177.0 is the most directional move in the recent window — it's the first step of a stated roadmap to cover more Bazel ecosystems.
ESPHome 2026.9.0 ships template climate component, OTA encryption with API key, and ESP-NOW for ESP32-P4
ESPHome 2026.9.0 is out, capping a beta cycle that added a template climate component (a long-requested flexible HVAC control primitive), OTA encryption keyed to the device's API key (hardening the update path), and ESP-NOW over hosted shim for the ESP32-P4. The beta cycle also included a systematic RAM allocation safety pass across the codebase — heap exhaustion now returns an error instead of panicking. Monthly releases continue landing at a consistent pace.
Semgrep is shipping weekly releases at a steady pace, advancing on two fronts: broader language and build-system coverage (Bazel/Maven via rules_jvm_external, OpenTofu, Solidity, Ruby parser improvements) and engine reliability (OCaml GC bug fixes, proxy handling, UTF-8 in MCP mode, better crash diagnostics). The Bazel supply chain milestone in v1.177.0 is the most directional move in the recent window — it's the first step of a stated roadmap to cover more Bazel ecosystems.
Semgrep is filling in supply chain coverage across the build-system ecosystem one lockfile format at a time. The parallel track is making the engine more trustworthy in edge cases: fixes for nondeterministic crashes, clearer error messages on signals and segfaults, and UTF-8/locale resilience. Neither track is finished — Bazel support explicitly lists rules_python, rules_go, and rules_js as follow-on work, and the performance wins suggest there's more headroom being found.
The next Bazel milestone will likely extend supply chain attribution to Python and JS ecosystems inside Bazel workspaces. Engine work will continue to be driven by edge-case reliability reports from CI deployments at scale.
ESPHome 2026.9.0 is out, capping a beta cycle that added a template climate component (a long-requested flexible HVAC control primitive), OTA encryption keyed to the device's API key (hardening the update path), and ESP-NOW over hosted shim for the ESP32-P4. The beta cycle also included a systematic RAM allocation safety pass across the codebase — heap exhaustion now returns an error instead of panicking. Monthly releases continue landing at a consistent pace.
ESPHome is expanding in two directions simultaneously: broader hardware support (ESP32-P4, BK72xx BLE, new platform components) and more robust runtime behavior (RAMAllocator pattern, use-after-free fixes, better BLE-WiFi coexistence). The template climate component is the most user-visible addition — it brings custom HVAC logic into ESPHome's declarative model, reducing the need for external Home Assistant automations. Audio stack (i2s, resampler, mixer) reliability is also a consistent focus.
The 2026.10.0 cycle will likely continue the RAMAllocator pattern across remaining allocating code paths and add more ESP32-P4-specific features. Audio (voice assistants, speakers) will stay a top area given the ongoing i2s reliability work.
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 Semgrep or ESPHome.
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
Skipper adds Redis as a distributed L2 cache backend amid a high-frequency patch cadence.
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 Semgrep alternatives → · See all ESPHome alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. ESPHome is currently shipping more aggressively (velocity 6.3 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. ESPHome is currently shipping more aggressively (velocity 6.3 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 Semgrep alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Semgrep alternatives" section above for the current picks, or visit /alternatives/semgrep for the full list with editorial commentary on each.
Top ESPHome alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "ESPHome alternatives" section above for the current picks, or visit /alternatives/esphome for the full list with editorial commentary on each.