Read 2026-10-23
fluent/fluentd: technical due diligence, read from its repository
What Borehole read in fluent/fluentd's code and history at f984d65: 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 | strong |
| Engineering Process & SDLC Maturity | strong |
| Product & Engineering Maturity | strong |
| Security & Reliability Posture | strong |
| Observability & Operations | not assessable |
| Fit with the Acquirer | not assessable |
What the repository says
GOVERNANCE.md:53: names CNCFREADME.md:7: names OpenSSF
Architecture & Codebase — including AI provenance
stronglib/fluent/plugin/output.rb is 1,689 lines, 12× this codebase's median file
adequateThe median source file here is 131 lines. 2 files exceed 1,310 lines, the largest being 1,689. 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.
lib/fluent/plugin/output.rb:1 — 1,689 lines (12× median) |
lib/fluent/supervisor.rb:1 — 1,348 lines (10× median) |
Engineering Process & SDLC Maturity
strongNo finding.
Product & Engineering Maturity
strongNo finding.
Security & Reliability Posture
strong2 deserialisers that can run code
adequate2 places read data with a deserialiser that executes what it reads (Ruby `Marshal.load`). That is safe on data the system wrote itself and remote code execution on anything else. Ask where each one's input comes from.
lib/fluent/command/fluentd.rb:24 — code-executing deserialiser |
lib/fluent/plugin/out_copy.rb:113 — code-executing deserialiser |
10 advisories against this project in the last 24 months, 7 high or critical
adequateThe newest was published on 2026-09-29. 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 2 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 1.20.0. Answer lives in: the release you run, set against each fixed version. The record is incomplete: NVD: 1 record names fluentd with nothing tying it to this repository (CVE-2026-54680).
| 2026-09-29: GHSA-x455-r5cg-h9p9 (low), fixed in 1.19.4: Incomplete Fix for CVE-2026-44160: DoS via Unbounded Decompression in Buffer Chunk Streaming |
| 2026-09-29: GHSA-g69w-f42r-xp35 (high), fixed in 1.19.4: Out-of-Memory DoS via Object Allocation Amplification in `in_http` ndjson parsing |
| 2026-09-29: GHSA-h3xv-5jpx-r4j2 (high), fixed in 1.19.4: Out-of-Memory DoS via Unbounded TCP/TLS Connection Buffer in `in_syslog` |
| 2026-09-29: GHSA-5hq3-r276-rfr5 (high), fixed in 1.19.4: Incomplete Fix for CVE-2026-44024: Path Traversal Bypass via Bare `..` Tag in Output Plugins |
| 2026-09-15: CVE-2026-44163 (moderate): fluent-plugin-opentelemetry is a Fluentd input and output plugin for forwarding OpenTelemetry Protocol data. Prior to 0.5.3, the in_opentelemetry HTTP input rea |
Observability & Operations
not assessableNot rated: only 5 of 16 checks could reach a conclusion here; the rest do not apply to this repository or could not read it.
Fit with the Acquirer
not assessableNot rated: structurally not assessable from a repository.
Read more, or read your own
The full report on fluent/fluentd: 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.