FOSSA CLI
fossa-cli's feed jumps from 3.17 to 3.20, with clearer container scan errors.
A side-by-side editorial comparison of Nautobot and NetBox — release velocity, themes, recent moves, and the top alternatives to consider.
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.
NetBox 4.7's patch run fixes a token leak and a broken restore path.
Four 4.7 patches followed the September 4.7.0 release. 4.7.1 reinstalled hierarchical-path triggers that a pg_dump restore silently dropped, 4.7.2 stopped background bulk requests recording plaintext API tokens in job results, 4.7.3 was a REST and GraphQL performance release, and 4.7.4 adds change-log IDs to webhook payloads, fixes the circuit status GraphQL enum and warns about a thumbnail storage change.
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.
Four 4.7 patches followed the September 4.7.0 release. 4.7.1 reinstalled hierarchical-path triggers that a pg_dump restore silently dropped, 4.7.2 stopped background bulk requests recording plaintext API tokens in job results, 4.7.3 was a REST and GraphQL performance release, and 4.7.4 adds change-log IDs to webhook payloads, fixes the circuit status GraphQL enum and warns about a thumbnail storage change.
The ltree migration in 4.7.0 is still generating follow-up work, and the patch notes are candid about what broke. Performance work on REST serialisation and GraphQL has been steady across the line, and event payloads are getting richer for automation users.
Expect further 4.7.x patches on a two-week rhythm with more API performance fixes; the entries don't show what 4.8 will contain.
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 Nautobot or NetBox.
fossa-cli's feed jumps from 3.17 to 3.20, with clearer container scan errors.
Gloo Gateway's October batch fixes proxies that silently kept stale endpoints.
Traefik v3.8 rc.1 is a Gateway API release; v2.11 keeps getting security patches.
Render's autumn changelog is plan tuning and runtime defaults while Workflows fills out.
Home Assistant keeps pulling hidden power-user features into the UI, now trigger IDs.
Alertmanager 0.34.2 turns off CORS by default, breaking cross-origin API calls.
See all Nautobot alternatives → · See all NetBox alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
Both compete on the same themes — security — within Infra & APIs. Nautobot and NetBox 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. Nautobot and NetBox 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 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.
Top NetBox alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "NetBox alternatives" section above for the current picks, or visit /alternatives/netbox for the full list with editorial commentary on each.