Borehole · Project · free tier
allinurl/goaccess
Free reading: not for reliance
fb62f16 · 4,519 commits · 148 files
Read 2026-11-07

allinurl/goaccess: technical due diligence, read from its repository

What Borehole read in allinurl/goaccess's code and history at fb62f16: 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 Postureadequate
Observability & Operationsadequate
Fit with the Acquirernot assessable

What the repository says

  • COPYING: Relicensed: GPL-2.0 → MIT (2016-03-11)

Architecture & Codebase — including AI provenance

strong
01.6

src/websocket.c is 3,196 lines, 13× this codebase's median file

adequate

The median source file here is 230 lines. 5 files exceed 2,300 lines, the largest being 3,196. 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
src/websocket.c:1 — 3,196 lines (13× median)
src/parser.c:1 — 2,735 lines (11× median)
src/tpl.c:1 — 2,677 lines (11× median)
resources/js/app.js:1 — 2,502 lines (10× median)
src/persistence.c:1 — 2,383 lines (10× median)

Engineering Process & SDLC Maturity

adequate
02.3

Tests are absent or token

adequate

0 test files against 90 source files (0.0%). 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
0 test files / 90 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: CI workflows. 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 148 tracked files

Product & Engineering Maturity

not assessable

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

Security & Reliability Posture

adequate
05.6

1 Dockerfile runs the application as root

adequate

No 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.

Evidence
Dockerfile — runs as root
05.27

The build runs third-party code it does not pin

adequate

4 third-party CI actions are referenced by a tag or branch rather than a commit, so they run whatever that tag points to on the day. Tags have been moved to malicious commits in real supply-chain attacks, and a piped script is whatever the server returns that minute. Pinning to a commit is the fix, and it is small.

Evidence
.github/workflows/deb-packaging-buildx.yml:79 — action pinned by tag
.github/workflows/deb-packaging-buildx.yml:82 — action pinned by tag
05.60

Relicensed: GPL-2.0 → MIT (2016-03-11)

adequate

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

Evidence
COPYING — GPL-2.0 from 2010-07-09
COPYING — MIT from 2016-03-11
05.65

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

adequate

The newest was published on 2026-09-21. A project that publishes advisories is telling its users about its fixes, and the count and pace say how much security work it carries. The record is incomplete: NVD: 1 record names goaccess with nothing tying it to this repository (CVE-2026-113678).

Evidence
2026-09-21: GHSA-4g8g-wj68-q4fp (high): Remote pre-auth DoS: NULL deref / OOB read on binary WebSocket frame (missing NUL-termination)
2026-07-20: GHSA-5gm5-pvh2-wg46 (moderate): GoAccess WebSocket server: signed 32 bit truncation of the 64 bit frame length causes a remote pre authentication denial of service
2026-07-20: GHSA-5phr-qpgf-hgrg (moderate): Out-of-bounds heap read in parse_ios() via crafted User-Agent (opesys.c:323) lead to remote crash/DoS
2026-07-20: GHSA-qcx5-vh2x-35fr (moderate): Heap Out-of-Bounds Write in GoAccess `parse_browser()`

Observability & Operations

adequate
06.2

No structured logging library is in use

adequate

Nothing 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.

Evidence
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
06.8

One request cannot be followed through the logs

adequate

Nothing 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.

Evidence
no request id, correlation id or tracing found
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
06.18

2 of 2 deployed images carry no version, or `latest`

adequate

2 images in the deployment configuration are named without a version or as `latest`. A redeploy can change the software without a commit, a rollback has nothing to roll back to, and nobody can say from the repository what is running.

Evidence
docker-compose/docker-compose.vanilla.yaml:3 — image without a version
docker-compose/docker-compose.vanilla.yaml:12 — image without a version

Fit with the Acquirer

not assessable

Not rated: structurally not assessable from a repository.

Read more, or read your own

The full report on allinurl/goaccess: 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.