crowdsecurity/crowdsec

CrowdSec - the open-source and participative security solution offering crowdsourced protection against malicious IPs and access to the most advanced...

View on GitHub ↗Jump to charts ↓Open shareable report

Summary Information

Updated 2 minutes ago
Added to GitGenius on September 4th, 2026
Created on May 15th, 2020
Open Issues & Pull Requests: 296 (+0)
GitHub issues: Enabled
Number of forks: 714
Total Stargazers: 14,785 (+0)
Total Subscribers: 123 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 1.5 hours
Mean response time: 55.1 days
90th percentile: 104.1 days
Tracked items: 380

How this project is maintained

Around half of the issues opened in the past year never receive a reply. 92% of open issues come from outside the core team, so the backlog reflects real-world use rather than internal planning. 67% of tracked open issues have had no activity in three months, so the open count overstates what is actively being worked. Only 3% of issues opened in the past year have been closed. Three people close 77% of everything that gets resolved.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 153
New in 7 days: 12
Closed in 7 days: 9
Avg open age: 516 days
Stale 30+ days: 133
Stale 90+ days: 123

Recent activity

Opened in 7 days: 11
Closed in 7 days: 9
Comments in 7 days: 0
Events in 7 days: 0

Top labels

  • needs/triage (372)
  • kind/bug (226)
  • needs/kind (96)
  • kind/enhancement (69)
  • os/linux (65)
  • triage/accepted (29)
  • kind/feature (15)
  • value/low (15)

Detailed Description

CrowdSec is an open-source intrusion detection and prevention system that combines log analysis with crowdsourced threat intelligence to detect and block malicious IP addresses.

The tool addresses the challenge of detecting coordinated attacks across distributed infrastructure by analyzing logs from multiple sources to identify suspicious patterns like brute force attempts, port scans, and web application attacks. It operates on a "Detect Here, Remedy There" model where detection happens centrally but remediation can be applied at different layers of the stack through pluggable remediation components called bouncers. The Security Engine functions as both an IDS/IPS and WAF, examining both system logs and HTTP requests. Users contribute threat data back to a community blocklist that all participants can use for proactive IP blocking, creating a participatory defense network.

Teams should adopt this tool if they operate modern, distributed infrastructure and want centralized threat detection without vendor lock-in. It suits environments where logs flow from multiple sources and where blocking decisions need to happen at various stack levels—application, system, or infrastructure. The project ships with default detection scenarios covering common attack patterns, but its hub-based extension system allows customization and addition of community-contributed rules. This makes it suitable for both standard deployments and specialized security requirements.

Development activity shows consistent testing infrastructure with automated Go tests and integration tests running on pull requests. The project maintains active community engagement through a Discord channel and social media presence. Documentation is comprehensive and kept alongside the codebase, indicating ongoing attention to user onboarding and clarity.