Oh Dear
Oh Dear's weekly changelogs have carried a security section five weeks running.
A side-by-side editorial comparison of CrowdSec and Node-RED — 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.
Node-RED 5.0.9 lets users drag-order flows in the explorer and adds error badges to tabs.
Node-RED maintains two lines. 5.0.9 is a larger-than-usual maintenance release: flows can be drag-ordered in the Explorer sidebar, tabs and the explorer show error badges, HTML script and style blocks get JavaScript and CSS support, Monaco moves to 0.57, and CSV, Range, RBE, Filter and MQTT nodes get fixes. 4.1.17 backports only the merge-conflict resolution fixes.
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.
Node-RED maintains two lines. 5.0.9 is a larger-than-usual maintenance release: flows can be drag-ordered in the Explorer sidebar, tabs and the explorer show error badges, HTML script and style blocks get JavaScript and CSS support, Monaco moves to 0.57, and CSV, Range, RBE, Filter and MQTT nodes get fixes. 4.1.17 backports only the merge-conflict resolution fixes.
The 5.x line is now taking editor usability work from a wider set of contributors, with six first-time contributors in 5.0.9. The 4.1.x branch stays on backports only. The feed shows no 5.1 or new major feature yet.
Expect more 5.0.x releases with editor improvements; the entries don't show when a 5.1 with larger features will arrive.
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 Node-RED.
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 Node-RED alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. CrowdSec and Node-RED 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. CrowdSec and Node-RED 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 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 Node-RED alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Node-RED alternatives" section above for the current picks, or visit /alternatives/node-red for the full list with editorial commentary on each.