Oh Dear
Oh Dear's weekly changelogs have carried a security section five weeks running.
Comparison · Infra & APIs
CrowdSec vs Gitness
A side-by-side editorial comparison of CrowdSec and Gitness — release velocity, themes, recent moves, and the top alternatives to consider.
CrowdSec vs Gitness: at a glance
What is CrowdSec?
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.
What is Gitness?
Harness Open Source last shipped in August 2025, on this feed at least
The feed holds two releases of Harness Open Source, tracked here as Gitness. v3.2.0 in May 2025 added Git LFS, default reviewers through branch rules and a Revert PR option; v3.3.0 that August added tag rules, a PR dashboard upgrade with favourite repositories, and a fix for a Git LFS upload path flaw. Nothing newer appears here.
CrowdSec vs Gitness: editorial side-by-side
CrowdSec
5.0INFRA · APIS
CrowdSec's 1.8.2 candidates let operators write their own bot fingerprints.
◆ Current state
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.
◆ Where it's heading
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.
◆ Prediction
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.
Gitness
0.0INFRA · APIS
Harness Open Source last shipped in August 2025, on this feed at least
◆ Current state
The feed holds two releases of Harness Open Source, tracked here as Gitness. v3.2.0 in May 2025 added Git LFS, default reviewers through branch rules and a Revert PR option; v3.3.0 that August added tag rules, a PR dashboard upgrade with favourite repositories, and a fix for a Git LFS upload path flaw. Nothing newer appears here.
◆ Where it's heading
Both releases deepen code-hosting governance: branch rules, then tag rules, plus review routing through Code Owners. That is parity work against established Git hosts rather than a new direction. With entries more than a year old, the feed shows where the project was heading in 2025, not where it is now.
◆ Prediction
The entries do not support a confident call: there is no release in this feed after v3.3.0, so it is unclear whether the project slowed or the feed stopped tracking it.
Alternatives to CrowdSec and Gitness
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 Gitness.
Apache ShenYu
ShenYu's AI gateway plugins are back in motion, with 2.7.2 candidate tags in October.
TestingBot
TestingBot's autumn work is plumbing: a rebuilt tunnel and another bug-tracker link.
KubeArmor
KubeArmor ships fixes as release-candidate tags, and its feed misses the finals.
All Quiet
All Quiet moves from enterprise integrations to the on-call engineer's own day.
Robusta
Robusta's recent releases patch its runner image rather than add features.
See all CrowdSec alternatives → · See all Gitness alternatives →
Recent activity from CrowdSec and Gitness
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 10d agoCrowdSec1.8.2 rc2 adds a WAF RateLimit helper and decision stream limits
- 19d agoCrowdSec1.8.2 rc1 adds custom JS fingerprinting for bot detection
- 2mo agoCrowdSec1.8 rc2 tunes the bot-detection challenge, hardens acquisition
- 3mo agoCrowdSecCrowdSec 1.8 RC adds WAF bot detection and a Kubernetes datasource ⚡
- 6mo agoCrowdSec1.7.8 RC: OpenAPI schema validation in the WAF
- 7mo agoCrowdSec1.7.7 RC: flexible WAF rule conditions and RE2 by default
- 1y agoGitnessHarness Open Source 3.3: tag rules, PR dashboard, LFS path fix
- 1y agoGitnessHarness Open Source 3.2: Git LFS, default reviewers, Revert PR
Frequently asked questions
What is the difference between CrowdSec and Gitness?
They serve adjacent needs but don't currently overlap on shipped themes. CrowdSec 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.
Is CrowdSec better than Gitness?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. CrowdSec 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.
What are the best alternatives to CrowdSec?
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.
What are the best alternatives to Gitness?
Top Gitness alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Gitness alternatives" section above for the current picks, or visit /alternatives/gitness for the full list with editorial commentary on each.