Borehole · Project · free tier
the-tcpdump-group/tcpdump
Free reading: not for reliance
eebca99 · 8,003 commits · 1,940 files
Read 2026-10-04

the-tcpdump-group/tcpdump: technical due diligence, read from its repository

What Borehole read in the-tcpdump-group/tcpdump's code and history at eebca99: 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 Maturityadequate
Product & Engineering Maturitynot assessable
Security & Reliability Posturenot assessable
Observability & Operationsnot assessable
Fit with the Acquirernot assessable

What the repository says

  • Releases are cut from another branch than the one surveyed

Architecture & Codebase — including AI provenance

strong
01.6

print-802_11.c is 3,591 lines, 16× this codebase's median file

adequate

The median source file here is 213 lines. 8 files exceed 2,130 lines, the largest being 3,591. 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
print-802_11.c:1 — 3,591 lines (16× median)
tcpdump.c:1 — 3,573 lines (16× median)
print-isoclns.c:1 — 3,547 lines (16× median)
print-isakmp.c:1 — 3,394 lines (15× median)
print-bgp.c:1 — 3,348 lines (15× median)

Engineering Process & SDLC Maturity

adequate
02.1

Little of the recent change carries a trace of review

adequate

In the last 24 months, 32 of 370 commits (8.6%) carry any trace of review: a merge, a pull-request reference, a Reviewed-by or Reviewed-on trailer, a Closes/Fixes reference, a maintainer's sign-off on someone else's change, or a change applied by someone other than its author. That is low but not absent. Review may happen in a workflow this history does not record; a buyer should ask how change is approved before it ships.

Evidence
32 of 370 commits in the last 24 months carry review evidence; 10.3% across all 8,003
02.3

Tests cover a thin slice of the codebase

adequate

10 test files against 269 source files (3.7%). This does not measure whether the tests are good, only whether enough of them exist for the codebase to be changed safely by someone who did not write it — which is exactly the situation after an acquisition.

Evidence
10 test files / 269 source files
02.6

Almost no process scaffolding exists in the repository

adequate

Of five ordinary markers — CI workflows, CODEOWNERS, a pull-request template, pre-commit hooks, contribution guidance — 1 is present: contribution guidance. Branch protection itself is a GitHub setting rather than a file, so this is a reading of proxies and not of the rules themselves. What it does establish is that the process is not written down anywhere a new engineer would find it.

Evidence
1 of 5 markers present across 1,940 tracked files

Product & Engineering Maturity

not assessable
04.5

Effort is shifting from building to rewriting

adequate

Deleted lines per line added rose from 0.35 to 0.81 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.

Evidence
first half 0.35, second half 0.81 (split 2013-03-30)
04.62

Releases are cut from another branch than the one surveyed

adequate

The newest release, tcpdump-4.99.7, is not on the branch this survey read; the newest release on it is tcpdump-4.6.0. The shipped product may differ from what this report describes. Survey the release branch too.

Evidence
tag tcpdump-4.99.7

Security & Reliability Posture

not assessable

Not rated: only 14 of 34 checks could reach a conclusion here; the rest do not apply to this repository or could not read it.

Observability & Operations

not assessable

Not rated: only 4 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 assessable

Not rated: structurally not assessable from a repository.

Read more, or read your own

The full report on the-tcpdump-group/tcpdump: 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.