Skipper
Skipper trims a 4x memory regression out of routesrv, days after shipping h2c
A side-by-side editorial comparison of OpenMQTTGateway and Verdaccio — release velocity, themes, recent moves, and the top alternatives to consider.
OpenMQTTGateway spent three years shedding its dependencies, then stopped shipping entirely.
The last release was January 2025, a single bug fix for adaptive scanning restarting the gateway. Before that, the project moved steadily toward standing alone: 1.8.0 embedded an MQTT broker via PicoMQTT so a gateway no longer needs an external server, 1.6.0 added a web interface so it no longer needs a home automation controller to configure, and 1.5.0 brought device trackers for presence detection with over-the-air updates from the controller. Hardware arrived alongside software, with the Theengs Bridge in 1.7.0 and the Theengs Plug in 1.3.0.
Verdaccio's 7.0 line is subtraction — forks dropped, toolchain swapped, tags mostly empty
The next-7 prerelease line is short and almost entirely maintenance. Its one substantive release adopted @verdaccio/server and deleted the local api, web, and storage forks, leaving a thin Storage wrapper behind only to keep callback-based storage plugins working. Everything since has been dependency retargeting, a lint and format toolchain swap, and a tag whose body reads 'chore: trigger release'.
The last release was January 2025, a single bug fix for adaptive scanning restarting the gateway. Before that, the project moved steadily toward standing alone: 1.8.0 embedded an MQTT broker via PicoMQTT so a gateway no longer needs an external server, 1.6.0 added a web interface so it no longer needs a home automation controller to configure, and 1.5.0 brought device trackers for presence detection with over-the-air updates from the controller. Hardware arrived alongside software, with the Theengs Bridge in 1.7.0 and the Theengs Plug in 1.3.0.
The arc through 1.2 to 1.8 is one of progressive independence — first from a controller for configuration, then from a broker for messaging — turning a bridge component into a self-contained device. Release intervals widened throughout: monthly in early 2023, then annual, then nothing for nineteen months. Whatever the roadmap was, the feed has not recorded activity since.
The evidence here does not support a confident prediction about what ships next; the project has published nothing in nineteen months. If it resumes, the unfinished thread is the embedded broker, which shipped in 1.8.0 and received only a scanning bug fix afterward.
The next-7 prerelease line is short and almost entirely maintenance. Its one substantive release adopted @verdaccio/server and deleted the local api, web, and storage forks, leaving a thin Storage wrapper behind only to keep callback-based storage plugins working. Everything since has been dependency retargeting, a lint and format toolchain swap, and a tag whose body reads 'chore: trigger release'.
This is consolidation ahead of a major: the project is collapsing code it had been carrying in-tree back onto shared packages and standardising tooling around oxlint and oxfmt. The remaining compatibility shim is the visible unfinished business — it exists purely for legacy plugins, and it is the last thing standing between this line and a clean server dependency.
Removing the legacy storage wrapper is the decision this line is heading toward, and it breaks callback-based storage plugins when it lands, so expect it to arrive with the 7.0.0 final rather than in another next tag. Until then the prerelease stream will keep producing tags with no user-visible content.
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 OpenMQTTGateway or Verdaccio.
Skipper trims a 4x memory regression out of routesrv, days after shipping h2c
CloudStack ships two LTS branches in lockstep and publishes nothing but pointers
Kinsta is moving MyKinsta's controls into its API, one surface per month
Observability lands on OpenTelemetry semconv in the LTS train
Canvas agents gain memory, and onboarding moves into the editor
Security and governance controls catch up to the Copilot build-out
See all OpenMQTTGateway alternatives → · See all Verdaccio alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Verdaccio is currently shipping more aggressively (velocity 2.5 vs 0.0), 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. Verdaccio is currently shipping more aggressively (velocity 2.5 vs 0.0), with 0 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 OpenMQTTGateway alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "OpenMQTTGateway alternatives" section above for the current picks, or visit /alternatives/openmqttgateway for the full list with editorial commentary on each.
Top Verdaccio alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Verdaccio alternatives" section above for the current picks, or visit /alternatives/verdaccio for the full list with editorial commentary on each.