Oh Dear
Oh Dear's weekly changelogs have carried a security section five weeks running.
A side-by-side editorial comparison of CrowdSec and Snort 3 — release velocity, themes, recent moves, and the top alternatives to consider.
CrowdSec's 1.8.2 candidates let operators write their own bot fingerprints.
The bot detection introduced with 1.8 is now being opened to customization. The 1.8.2 candidates add custom JavaScript fingerprinting, a cscli bot subcommand and a FlagSubmission helper, and rc2 adds a RateLimit helper for the WAF plus a cookie option for embedded contexts. Operational work runs alongside it: a cs_features metric, optional limits on concurrent decision streams and TLS certificate reloads.
Snort 3.12.4 pairs a long memory-safety pass with detection speed work
Snort 3.12.4.0 rolls up changes since 3.12.2.0 and is the first release in this feed since April. It fixes reject and react actions in IDS mode, a TLS decryption bypass case with adaptive profiles, and many bounds and memory issues across dce_rpc, dns, decompress and appid. It also reorganizes detection data for cache efficiency and expands extractor logging.
The bot detection introduced with 1.8 is now being opened to customization. The 1.8.2 candidates add custom JavaScript fingerprinting, a cscli bot subcommand and a FlagSubmission helper, and rc2 adds a RateLimit helper for the WAF plus a cookie option for embedded contexts. Operational work runs alongside it: a cs_features metric, optional limits on concurrent decision streams and TLS certificate reloads.
The WAF remains the center of gravity, and the direction is programmability. RateLimit, SkipProcessing and the fingerprinting hooks give rule authors primitives rather than fixed behavior. The LAPI changes point at larger deployments, where decision streaming puts load on the central API.
The final 1.8.2 is dated 26 October on GitHub, though it has not reached this feed yet. Whether fingerprint data ever joins the community blocklist remains unanswered in these notes.
Snort 3.12.4.0 rolls up changes since 3.12.2.0 and is the first release in this feed since April. It fixes reject and react actions in IDS mode, a TLS decryption bypass case with adaptive profiles, and many bounds and memory issues across dce_rpc, dns, decompress and appid. It also reorganizes detection data for cache efficiency and expands extractor logging.
The two earlier threads are both still present, but memory safety now outweighs new appid capability. A notable share of the fixes bound inputs or cap unbounded growth, in DNS over TCP, VBA decompression and SMB transactions, which suggests systematic hardening. Detection hot-path tuning is newer here, as are extractor changes that bring output closer to connection logging.
Expect the same hardening pattern to continue across parsers, with extractor output the most likely area for further visible change. The six-month gap in this feed leaves the release cadence unclear.
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 CrowdSec or Snort 3.
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 CrowdSec alternatives → · See all Snort 3 alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. CrowdSec is currently shipping more aggressively (velocity 5.0 vs 2.5), 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. CrowdSec is currently shipping more aggressively (velocity 5.0 vs 2.5), 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 CrowdSec alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "CrowdSec alternatives" section above for the current picks, or visit /alternatives/crowdsec for the full list with editorial commentary on each.
Top Snort 3 alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Snort 3 alternatives" section above for the current picks, or visit /alternatives/snort for the full list with editorial commentary on each.