Oh Dear
Oh Dear's weekly changelogs have carried a security section five weeks running.
A side-by-side editorial comparison of BorgBackup and Nautobot — release velocity, themes, recent moves, and the top alternatives to consider.
Borg 2.0 beta 25 breaks repositories to swap its hash and repository format.
BorgBackup's 2.0 beta line is still making breaking format changes. Beta 25 requires new repositories: it moves store object names to blake3, replaces several repository objects with an ini-style config, removes the none-sha256 and none-blake3 modes in favor of authenticated ones, and protects lock, index and cache objects with the repository key. The stable 1.4 line remains the production track.
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.
BorgBackup's 2.0 beta line is still making breaking format changes. Beta 25 requires new repositories: it moves store object names to blake3, replaces several repository objects with an ini-style config, removes the none-sha256 and none-blake3 modes in favor of authenticated ones, and protects lock, index and cache objects with the repository key. The stable 1.4 line remains the production track.
Twenty-five betas in, the format is not settled, but this beta is decisive: it removes old modes and object types, which narrows what 2.0 has to support. Treating lock and cache objects as keyed data also extends the security model beyond archive contents.
Further betas are likely to keep requiring new repositories until the format freezes, so a release candidate should not be assumed soon. The 1.4 line stays the safe choice until then.
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 BorgBackup or Nautobot.
Oh Dear's weekly changelogs have carried a security section five weeks running.
ShenYu's AI gateway plugins are back in motion, with 2.7.2 candidate tags in October.
TestingBot's autumn work is plumbing: a rebuilt tunnel and another bug-tracker link.
KubeArmor ships fixes as release-candidate tags, and its feed misses the finals.
All Quiet moves from enterprise integrations to the on-call engineer's own day.
Robusta's recent releases patch its runner image rather than add features.
See all BorgBackup 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. Nautobot is currently shipping more aggressively (velocity 5.0 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. Nautobot is currently shipping more aggressively (velocity 5.0 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 BorgBackup alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "BorgBackup alternatives" section above for the current picks, or visit /alternatives/borgbackup 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.