Borehole · Project · free tier
crowdsecurity/crowdsec
Free reading: not for reliance
849c7a2 · 2,829 commits · 1,802 files
Read 2026-11-03

crowdsecurity/crowdsec: technical due diligence, read from its repository

What Borehole read in crowdsecurity/crowdsec's code and history at 849c7a2: its licence, security advisories, releases, review practice, tests, dependencies and operations. Every finding cites the file and line it rests on. The full report also covers the team and asks the questions the code cannot answer.

DimensionRating
Architecture & Codebase — including AI provenancestrong
Engineering Process & SDLC Maturitystrong
Product & Engineering Maturityadequate
Security & Reliability Postureadequate
Observability & Operationsstrong
Fit with the Acquirernot assessable

What the repository says

  • .gitmodules:1: 5 submodule(s) this survey does not read: test/lib/bats-core, test/lib/bats-file, test/lib/bats-assert

Architecture & Codebase — including AI provenance

strong
01.6

pkg/database/ent/mutation.go is 11,599 lines, 117× this codebase's median file

adequate

The median source file here is 99 lines. 13 files exceed 1,000 lines, the largest being 11,599. Size is not a defect on its own — some problems genuinely live in one place — but these are where merge conflicts, review fatigue and single-owner knowledge concentrate, and they are the first thing that slows an inheriting engineer down.

Evidence
pkg/database/ent/mutation.go:1 — 11,599 lines (117× median)
pkg/appsec/appsec.go:1 — 2,245 lines (22× median)
pkg/database/ent/client.go:1 — 1,924 lines (19× median)
pkg/database/ent/alert/where.go:1 — 1,814 lines (18× median)
pkg/database/ent/machine_create.go:1 — 1,642 lines (16× median)

Engineering Process & SDLC Maturity

strong

No finding.

Product & Engineering Maturity

adequate
04.3

101 direct dependencies in a single manifest

adequate

go.mod declares 101 direct dependencies. Each one is a maintenance obligation, a supply-chain surface and a potential licence question that transfers with the asset. The count says nothing about whether any given dependency was a good choice; it says how many such choices a buyer inherits.

Evidence
go.mod — 101 declared
04.37

API v1 and v2 have been served together for 72 months

adequate

v2 first appeared in Nov 2020, and v1 is still in the code 72 months later. Two versions mean two surfaces to secure, document and support. Ask who still calls the old one, and whether retiring it is planned.

Evidence
pkg/apiserver/controllers/controller.go — v1 since Nov 2020
pkg/apiserver/controllers/controller.go — v2 since Nov 2020

Security & Reliability Posture

adequate
05.13

10 outbound calls can wait forever

adequate

10 HTTP calls use a client with no timeout (Python `requests` without `timeout=`, or Go's default client). When a dependency slows down, each one holds a worker until the connection gives up, and enough of them take the service down with the dependency.

Evidence
cmd/crowdsec-cli/clisupport/support.go:123 — outbound call without a timeout
cmd/crowdsec-cli/clisupport/support.go:399 — outbound call without a timeout
cmd/crowdsec-cli/core/require/branch.go:29 — outbound call without a timeout
05.26

1 locked dependency has published vulnerabilities, 2 high or critical in what ships

adequate

1 of 275 locked dependencies match 6 published advisories in OSV, 2 of them rated high or critical. A lockfile says which version is installed, not whether the flawed code is reachable from this product, so each needs a look. Most are fixed by an upgrade, and the advisory names the version.

Evidence
go.mod — github.com/corazawaf/coraza/v3 v3.8.0: GHSA-6gcq-wc29-5xf2 (high), fixed in 3.8.1
05.65

5 advisories against this project in the last 24 months, 1 high or critical

adequate

The newest was published on 2026-10-27. A project that publishes advisories is telling its users about its fixes, and the count and pace say how much security work it carries. None of them affects the surveyed version. The record is incomplete: NVD: 1 record names crowdsec with nothing tying it to this repository (CVE-2026-61718).

Evidence
2026-10-27: GHSA-g9hc-g4w6-4mfx (low): Hardcoded InsecureSkipVerify disables TLS certificate validation in notification-splunk plugin
2026-08-31: GHSA-rh69-4vqj-9gj8 (moderate), fixed in 1.8.0: Unbounded request-body read in kubernetes-audit acquisition webhook (memory-exhaustion DoS)
2026-08-31: GHSA-g2x2-jgfg-pg7g (moderate), fixed in 1.8.0: HTTP acquisition datasource lacks a decompressed body cap and trusts Content-Length
2026-05-27: GHSA-273h-gvwr-c3qj (moderate), fixed in 1.7.8: CrowdSec LAPI: Denial of Service via Unbounded Gzip Decompression
2026-05-27: GHSA-rw47-hm26-6wr7 (high), fixed in 1.7.8: CrowdSec AppSec silently drops request body for chunked / HTTP-2 requests

Observability & Operations

strong
06.9

No error reporter is wired in

adequate

Nothing in the service initialises an error reporter (Sentry, Rollbar, Bugsnag, Honeybadger or an APM agent). An exception in production reaches a person only if someone is reading the logs, which usually means a customer reports it first.

Evidence
no error reporter initialised

Fit with the Acquirer

not assessable

Not rated: structurally not assessable from a repository.

Read more, or read your own

The full report on crowdsecurity/crowdsec: every dimension, the questions for the room, and the audit log.

Survey a repository: free on public repositories. Private code is read on your own machine by a collector whose source you can read first.