[PR #3992] [CLOSED] Add CrowdSec #21086

New Issue

GiteaMirror · 2026-05-08T00:11:08-05:00

GiteaMirror commented

2026-05-08 00:11:08 -05:00

📋 Pull Request Information

Original PR: https://github.com/sindresorhus/awesome/pull/3992
Author: @wolffcatskyy
Created: 3/9/2026
Status: ❌ Closed

Base: main ← Head: add-crowdsec

📝 Commits (1)

8aed1b0 Add CrowdSec

📊 Changes

1 file changed (+1 additions, -0 deletions)

View changed files

📝 readme.md (+1 -0)

📄 Description

https://github.com/wolffcatskyy/awesome-crowdsec#readme

CrowdSec is an open-source collaborative security stack that analyzes behaviors and responds to attacks, with a community-driven threat intelligence network.

By submitting this pull request I confirm I've read and complied with the below requirements 🖖

Requirements for your pull request

Don't open a Draft / WIP pull request while you work on the guidelines. A pull request should be 100% ready and should adhere to all the guidelines when you open it.
Don't waste my time. Do a good job, adhere to all the guidelines, and be responsive.
You have to review at least 4 other open pull requests. I reviewed #3981, #3980, #3960, and #3957 with detailed feedback.
You have read and understood the instructions for creating a list.
This pull request has a title in the format Add Name of List. It should not contain the word Awesome.
Your entry here should include a short description of the project/theme of the list. It should not describe the list itself.
Your entry should be added at the bottom of the appropriate category.
The title of your entry should be title-cased and the URL to your list should end in #readme.
No blockchain-related lists.
The suggested Awesome list complies with the below requirements.

Requirements for your Awesome list

Has been around for at least 30 days. (Note: The repo was created on Feb 16, 2026. I am submitting now for tracking purposes and will wait for the 30-day mark before expecting a merge. Please keep open or I can resubmit after March 18, 2026.)
Run awesome-lint on your list and fix the reported issues.
The default branch should be named main, not master.
Includes a succinct description of the project/theme at the top of the readme.
It's the result of hard work and the best I could possibly produce.
The repo name of your list should be in lowercase slug format: awesome-crowdsec.
The heading title of your list should be in title case format: # Awesome CrowdSec.
Non-generated Markdown file in a GitHub repo.
The repo should have awesome-list & awesome as GitHub topics.
Not a duplicate. I searched for existing submissions.
Only has awesome items. Curated 45+ high-quality resources.
Does not contain items that are unmaintained, archived, deprecated, or missing docs.
Entries have a description.
Includes the Awesome badge.
Has a Table of Contents section named Contents.
Has an appropriate license: CC0-1.0.
Has contribution guidelines (CONTRIBUTING.md).
Has consistent formatting and proper spelling/grammar.
Does not use hard-wrapping.
Does not include a CI badge.
Does not include an "Inspired by" link.

unicorn

🤖 This response was generated by Claude AI assisting the maintainer.

_{🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.}

## 📋 Pull Request Information **Original PR:** https://github.com/sindresorhus/awesome/pull/3992 **Author:** [@wolffcatskyy](https://github.com/wolffcatskyy) **Created:** 3/9/2026 **Status:** ❌ Closed **Base:** `main` ← **Head:** `add-crowdsec` --- ### 📝 Commits (1) - [`8aed1b0`](https://github.com/sindresorhus/awesome/commit/8aed1b0ece1c98f10e3857b2c2b0c0c70064e744) Add CrowdSec ### 📊 Changes **1 file changed** (+1 additions, -0 deletions) <details> <summary>View changed files</summary> 📝 `readme.md` (+1 -0) </details> ### 📄 Description **https://github.com/wolffcatskyy/awesome-crowdsec#readme** **CrowdSec is an open-source collaborative security stack that analyzes behaviors and responds to attacks, with a community-driven threat intelligence network.** ### By submitting this pull request I confirm I've read and complied with the below requirements 🖖 ## Requirements for your pull request - [x] Don't open a Draft / WIP pull request while you work on the guidelines. A pull request should be 100% ready and should adhere to all the guidelines when you open it. - [x] **Don't waste my time.** Do a good job, adhere to all the guidelines, and be responsive. - [x] **You have to review at least 4 other [open pull requests](https://github.com/sindresorhus/awesome/pulls?q=is%3Apr+is%3Aopen).** I reviewed #3981, #3980, #3960, and #3957 with detailed feedback. - [x] You have read and understood the [instructions for creating a list](https://github.com/sindresorhus/awesome/blob/main/create-list.md). - [x] This pull request has a title in the format `Add Name of List`. It should not contain the word `Awesome`. - [x] Your entry here should include a short description of the project/theme of the list. **It should not describe the list itself.** - [x] Your entry should be added at the bottom of the appropriate category. - [x] The title of your entry should be title-cased and the URL to your list should end in `#readme`. - [x] No blockchain-related lists. - [x] The suggested Awesome list complies with the below requirements. ## Requirements for your Awesome list - [ ] **Has been around for at least 30 days.** *(Note: The repo was created on Feb 16, 2026. I am submitting now for tracking purposes and will wait for the 30-day mark before expecting a merge. Please keep open or I can resubmit after March 18, 2026.)* - [x] Run [`awesome-lint`](https://github.com/sindresorhus/awesome-lint) on your list and fix the reported issues. - [x] The default branch should be named `main`, not `master`. - [x] **Includes a succinct description of the project/theme at the top of the readme.** - [x] It's the result of hard work and the best I could possibly produce. - [x] The repo name of your list should be in lowercase slug format: `awesome-crowdsec`. - [x] The heading title of your list should be in title case format: `# Awesome CrowdSec`. - [x] Non-generated Markdown file in a GitHub repo. - [x] The repo should have `awesome-list` & `awesome` as GitHub topics. - [x] Not a duplicate. I searched for existing submissions. - [x] Only has awesome items. Curated 45+ high-quality resources. - [x] Does not contain items that are unmaintained, archived, deprecated, or missing docs. - [x] Entries have a description. - [x] Includes the Awesome badge. - [x] Has a Table of Contents section named `Contents`. - [x] Has an appropriate license: CC0-1.0. - [x] Has contribution guidelines (`CONTRIBUTING.md`). - [x] Has consistent formatting and proper spelling/grammar. - [x] Does not use hard-wrapping. - [x] Does not include a CI badge. - [x] Does not include an "Inspired by" link. unicorn --- 🤖 *This response was generated by Claude AI assisting the maintainer.* --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>

GiteaMirror added the pull-request label 2026-05-08 00:11:08 -05:00

GiteaMirror closed this issue

2026-05-08 00:11:14 -05:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/awesome-sindresorhus#21086