readystack/crowdsec repository overview

⁠CrowdSec

readystack/crowdsec:v1.8.2-CE-ubuntu24.04-r3

Source, recipe and records

• Source and build recipe: https://readystack.dev/products/crowdsec/recipe⁠
• Upstream source at this release's pinned commit (v1.8.2): https://github.com/crowdsecurity/crowdsec/tree/3d369d64eb3e9ba770ed39aedc83ffd3170aef4c⁠
• Product page: https://readystack.dev/products/crowdsec⁠
• Hermetic Build Kit for this release (free with an account): https://readystack.dev/products/crowdsec⁠
• Release history (JSON): https://readystack.dev/api/releases/crowdsec⁠
• Defect record: https://readystack.dev/defects.html?product=crowdsec⁠
• Today's scan: https://readystack.dev/products/crowdsec#pp-grade⁠
• Report an issue: https://github.com/ReadyStackFree/readystack/issues/new?template=bug.yml&product=crowdsec⁠
• Signing key (cosign): https://readystack.dev/keys/cosign.pub⁠

A cosign-signed build of github.com/crowdsecurity/crowdsec v1.8.2 (MIT), built clean-room from official upstream source by ReadyStack⁠.

⁠Who uses it and why

Who: System administrators, DevOps and SRE teams who need to spot and block attacks on internet-facing servers.

Why: CrowdSec's Security Engine reads logs and HTTP requests, detects behaviour such as brute force and scans, and has a firewall or reverse proxy block the offending IP addresses.

Use case: A web server's logs show constant password guessing against its login page. CrowdSec parses those logs, recognises the brute-force pattern, and a remediation component on the firewall blocks the source address, without anyone writing ban rules by hand. Attacks it reports feed a shared community blocklist.

About the upstream project, written from its own description: https://github.com/crowdsecurity/crowdsec⁠ · https://docs.crowdsec.net/⁠

⁠What you get

Signature, user and attestations below were measured on the published digest sha256:207c64cf00e6edec760ab2df3dc7b88bcde017b57e3a03268c708d1dff4f27e8 on 2026-11-12.

• Scan scores — we scan every image we publish every day (an SBOM made with syft, vulnerabilities matched with grype, scored with cerodeo-v2, ce.rodeo's current rubric; scans before 2026-11-08 used cerodeo-v1) and record each scan with how its score was derived. This release's first and latest scan: https://readystack.dev/products/crowdsec⁠
• ReadyStack release check — passed at release on 2026-11-12: no fixable critical or high vulnerability (Docker Scout and OSV), a non-root user, SBOM and provenance attached. This is ReadyStack's own test, not a Docker grade; vulnerabilities published since then are in today's result at https://readystack.dev/queue⁠.
• Signed — cosign signature by the ReadyStack release key (fingerprint 04daa92344a52dbc) on this release's index digest sha256:207c64cf00e6edec760ab2df3dc7b88bcde017b57e3a03268c708d1dff4f27e8; verify with cosign verify --key https://readystack.dev/keys/cosign.pub readystack/crowdsec:v1.8.2-CE-ubuntu24.04-r3.
• Attestations — An SPDX SBOM and SLSA v1 build provenance are attached to this digest.
• Runs as a non-root user (crowdsec).
• Built from source by ReadyStack.

⁠Which tag should I pull?

This image follows the ReadyStack release-tag convention:

• The current release is v1.8.2-CE-ubuntu24.04-r3 — the release listed at readystack.dev. Release tags use the pattern <upstream-version>-CE-<base-os>-r<N>; the current one is signed, attested (SBOM + provenance), and is provided under the ReadyStack Agreement⁠.

• Earlier release tags (an older version or revision in the same pattern) are superseded. They stay pullable so existing deployments can pin them, but they are no longer re-graded, and fixes appear only in newer releases: move to the current release. For a superseded release's build kit, ask support.

• Release tags never move, so pulling the same tag again never changes the image. To be offered each new release automatically (a new revision r<N+1>, or a new upstream version), use the ReadyStack Renovate preset: https://readystack.dev/updates.html⁠

• Any tag beginning with internal- is an engineering-pipeline artifact published for build observability. It is unsupported, may change or disappear without notice, and must not be used in production.

# ✓ current release
docker pull readystack/crowdsec:v1.8.2-CE-ubuntu24.04-r3

# ✗ unsupported (do not pull)
docker pull readystack/crowdsec:internal-...

This release is signed; verify it with cosign verify --key https://readystack.dev/keys/cosign.pub readystack/crowdsec:v1.8.2-CE-ubuntu24.04-r3 (the signature is recorded in the public Sigstore transparency log). Support: [email protected]⁠, as set out in the ReadyStack Agreement⁠.

⁠Deployment

A single container running the CrowdSec Local API (LAPI) only (crowdsec -c /etc/crowdsec/config.yaml -no-cs), with the cscli tool beside it. The LAPI stores decisions and alerts and answers the security bouncers that ask for ban decisions and the log-processing agents that send alerts. Its database is an embedded SQLite file, /var/lib/crowdsec/data/crowdsec.db, so there is no separate database, sidecar or web UI.

docker run -d --name crowdsec -p 8080:8080 -v crowdsec-data:/var/lib/crowdsec readystack/crowdsec:v1.8.2-CE-ubuntu24.04-r3

The metrics port 6060 is not published here: it answers without credentials, so let Prometheus reach it over a private Docker network, or publish it only on a trusted interface, e.g. -p 127.0.0.1:6060:6060.

⁠The full ReadyStack Hermetic Build Kit

The complete --network=none build kit for this image — plus admin/DB/API handbooks, the build's validation records, and its build provenance records — is a free download for any registered account at readystack.dev/products/crowdsec⁠. A clean-room rebuild from this release's archive on an egress-blocked host reproduced its linux/amd64 digest sha256:9e8d24890818de97b10cd6a3225506ade1693863cd2fa60391e8f3b37fbd762e on 2026-11-12.

— ReadyStack · readystack.dev