Verdaccio
Verdaccio's v9 pre-release counter reaches 41, and the notes still say nothing
A side-by-side editorial comparison of Lima and Nautobot — release velocity, themes, recent moves, and the top alternatives to consider.
Lima 2.3 nears release, with a Windows path that drops QEMU and a new TUI
Lima v2.3.0-rc.0 is out with an experimental HCS driver that removes the QEMU dependency on Windows hosts, block device attachment for VZ guests on macOS, and experimental shared, host and bridged networks on Linux hosts. limactl menu adds a menu-based interface, which now opens when limactl runs on a terminal without arguments. The default Ubuntu template moves to 26.10.
Nautobot's October releases are a permissions audit: objects users can't view kept leaking.
Nautobot's 3.2 and 2.4 lines have shipped same-day security releases every two weeks since September. v3.2.8 and v2.4.45 lead with stored XSS fixes and a long run of cases where jobs, imports and REST related-object handling accepted or revealed objects the user could not view, including other users' API tokens. v3.2.7 and v2.4.44 closed a Jinja2 sandbox escape and added timeouts for regular-expression evaluation. v3.2.6 moved SSO login to HTTP POST, breaking bookmarked SSO URLs.
Lima v2.3.0-rc.0 is out with an experimental HCS driver that removes the QEMU dependency on Windows hosts, block device attachment for VZ guests on macOS, and experimental shared, host and bridged networks on Linux hosts. limactl menu adds a menu-based interface, which now opens when limactl runs on a terminal without arguments. The default Ubuntu template moves to 26.10.
The any-guest, any-host direction now reaches all three desktop platforms in one release, and each host gets a feature suited to its own virtualization stack. The menu interface is a different kind of addition: it aims at people who do not want to memorize the CLI. LFX mentees and outside contributors continue to carry much of this work, and the project's experimental-first labeling still applies to the biggest items.
A 2.3.0 final is the next step after rc.0. The HCS driver and Linux network modes should stay experimental there, following the pattern earlier platform additions took.
Nautobot's 3.2 and 2.4 lines have shipped same-day security releases every two weeks since September. v3.2.8 and v2.4.45 lead with stored XSS fixes and a long run of cases where jobs, imports and REST related-object handling accepted or revealed objects the user could not view, including other users' API tokens. v3.2.7 and v2.4.44 closed a Jinja2 sandbox escape and added timeouts for regular-expression evaluation. v3.2.6 moved SSO login to HTTP POST, breaking bookmarked SSO URLs.
Permissions were already the sustained theme in August, and the work has moved from Saved Views to the general paths every App relies on. New helpers such as restrict_queryset() and mock_wsgi_request() in the apps API, plus the fixes in WritableNestedSerializer, hand the same checks to App developers. The number of advisories per release points to a systematic review rather than a single report.
Expect App authors to be pointed at those helpers, and further advisories in the same object-visibility class in the next paired releases. v3.2.8's warning that Pillow 13 cannot run on Python 3.10 makes that version's support the likely next removal.
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 Lima or Nautobot.
Verdaccio's v9 pre-release counter reaches 41, and the notes still say nothing
Snort 3.12.4 pairs a long memory-safety pass with detection speed work
Nineteen patches into 3.2, HAProxy's ingress controller is mostly bumping dependencies
Honeycomb is working on the first ten minutes, not just the incident
Talos 1.15's alpha keeps moving: a silent containerd config trap and declarative CPU control
Pinot 1.6 adds SQL DDL and vector backends, and now needs Java 25 to run its services.
See all Lima alternatives → · See all Nautobot alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Lima and Nautobot are shipping at a similar cadence (velocity 5.0 vs 5.0, both within Sparkpulse's "active" band). 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. Lima and Nautobot are shipping at a similar cadence (velocity 5.0 vs 5.0, both within Sparkpulse's "active" band). For your specific use case, the alternatives sections above list other Infra & APIs products to evaluate alongside.
Top Lima alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Lima alternatives" section above for the current picks, or visit /alternatives/lima for the full list with editorial commentary on each.
Top Nautobot alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Nautobot alternatives" section above for the current picks, or visit /alternatives/nautobot for the full list with editorial commentary on each.