Read 2026-10-22
falcosecurity/falco: technical due diligence, read from its repository
What Borehole read in falcosecurity/falco's code and history at 4cea537: 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.
| Dimension | Rating |
|---|---|
| Architecture & Codebase — including AI provenance | adequate |
| Engineering Process & SDLC Maturity | strong |
| Product & Engineering Maturity | adequate |
| Security & Reliability Posture | adequate |
| Observability & Operations | adequate |
| Fit with the Acquirer | not assessable |
What the repository says
- Releases are cut from another branch than the one surveyed
COPYING: Relicensed: GPL-with-exception → GPL-2.0 (2018-06-18) → Apache-2.0 (2018-09-20)README.md:5: names OpenSSFREADME.md:13: names Cloud Native Computing Foundation.gitmodules:1: 1 submodule(s) this survey does not read: submodules/falcosecurity-rules
Architecture & Codebase — including AI provenance
adequate1 base image floats: no version, or `latest`
adequate1 of 4 `FROM` lines in product Dockerfiles name an image without a version, or with `latest`. Each build pulls whatever the registry serves that day, so the image that ships can change without a commit, and last month's build cannot be reproduced. Pin a version, or a digest.
docker/falco/Dockerfile:1 — base image without a version |
Engineering Process & SDLC Maturity
strongNo finding.
Product & Engineering Maturity
adequateEffort is shifting from building to rewriting
adequateDeleted lines per line added rose from 0.46 to 0.87 between the first and second halves of this history. Rework is normal and often healthy, but a rising ratio means an increasing share of the team's time is spent replacing code that already exists rather than building what does not. Whether that is deliberate repayment or churn is a question for the team.
| first half 0.46, second half 0.87 (split 2021-06-05) |
16% of bug fixes add or change a test
adequateOf 189 fixes in the last 24 months, 30 touched a test. A fix without the test that would have caught the bug can quietly come back, and the suite never learns from what went wrong.
| 30 of 189 |
Releases are cut from another branch than the one surveyed
adequateThe newest release, 0.45.1, is not on the branch this survey read; the newest release on it is 0.32.1. The shipped product may differ from what this report describes. Survey the release branch too.
| tag 0.45.1 |
Security & Reliability Posture
adequate3 Dockerfiles run the application as root
adequateNo USER instruction switches away from root, so the process runs with full privileges inside the container. It is a one-line fix and an ordinary expectation, which is why its absence is worth asking about: it usually says more about whether anyone has reviewed the deployment than about this container specifically.
docker/driver-loader-buster/Dockerfile — runs as root |
docker/driver-loader/Dockerfile — runs as root |
docker/falco-debian/Dockerfile — runs as root |
Relicensed: GPL-with-exception → GPL-2.0 (2018-06-18) → Apache-2.0 (2018-09-20)
adequateThe root licence changed 2 time(s). Code taken under earlier terms stays under them; check which terms any fork or customer relied on.
1 advisory against this project in the last 24 months
adequateThe newest was published on 2025-04-30. A project that publishes advisories is telling its users about its fixes, and the count and pace say how much security work it carries. Whether 1 of them are fixed in the code you ship could not be told from this history: its version is only known to be at least 0.32.1. Answer lives in: the release you run, set against each fixed version. The record is incomplete: NVD: 1 record names falco with nothing tying it to this repository (CVE-2026-39292).
| 2025-04-30: GHSA-7cq5-h4p2-h37p (low), fixed in 0.40 with krsi plugin: Unsupported detection of asynchronous io_uring operations |
Observability & Operations
adequateNo telemetry or error reporting is wired in anywhere
adequateNone of 341 readable files references an instrumentation, metrics or error-reporting library. If this system is in production, nobody learns that it broke from the system itself — they learn it from a customer. That is a reliability finding before it is an observability one.
| searched 341 tracked text files for 16 known instrumentation libraries; manifests for metrics, tracing and error-reporting families; locked dependencies for the packages that emit; 0 matched |
No structured logging library is in use
adequateNothing references a structured logging library. Logs that are written to be read by a person are not searchable by a machine, which means incident response here is proportional to how well someone remembers the codebase rather than to what the tooling can find.
| C++ source is not searched: C++ programs log through printf-style calls unless they take a library, and none of the 10 searched for is referenced |
One request cannot be followed through the logs
adequateNothing in the service carries a request or correlation id, and there is no tracing. When a customer reports a failure, the log lines that belong to their request cannot be picked out from everyone else's.
| no request id, correlation id or tracing found |
No error reporter is wired in
adequateNothing 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.
| no error reporter initialised |
Fit with the Acquirer
not assessableNot rated: structurally not assessable from a repository.
Read more, or read your own
The full report on falcosecurity/falco: 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.