apache/kafka: technical due diligence, read from its repository

The median source file here is 113 lines. 75 files exceed 1,130 lines, the largest being 10,189. 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.

39 files were marked deprecated over two years ago and still are, the oldest since Apr 2019. A deprecation is a promise to remove. Ask what still depends on these, and whether removing them is scheduled.

The newest release, 4.4.0, is not on the branch this survey read; the newest pre-release on it is 0.8.0-beta1. The shipped product may differ from what this report describes. Survey the release branch too.

Dependency versions are declared as ranges and no lockfile is committed, so a build today does not necessarily produce what a build last month produced. That matters twice over in a transaction: the thing being bought cannot be reproduced exactly, and a compromised upstream release arrives without anyone choosing to take it.

The root licence changed 3 time(s). Code taken under earlier terms stays under them; check which terms any fork or customer relied on.

The newest was published on 2026-09-16. 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 11 of them are fixed in the code you ship could not be told from this history. Answer lives in: the release you run, set against each fixed version. The record is incomplete: NVD: 37 records name kafka with nothing tying them to this repository (CVE-2016-10693, CVE-2023-29471, CVE-2023-34040, …).

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.