Borehole · Project · free tier
gitlab.com/gitlab-org/gitlab-runner
Free reading: not for reliance
0e3fe7d · 15,564 commits · 1,444 files
Read 2026-10-04

gitlab.com/gitlab-org/gitlab-runner: technical due diligence, read from its repository

What Borehole read in gitlab.com/gitlab-org/gitlab-runner's code and history at 0e3fe7d: 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 Maturitystrong
Product & Engineering Maturityadequate
Security & Reliability Postureadequate
Observability & Operationsstrong
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

executors/kubernetes/kubernetes.go is 3,939 lines, 35× this codebase's median file

adequate

The median source file here is 111 lines. 7 files exceed 1,110 lines, the largest being 3,939. 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
executors/kubernetes/kubernetes.go:1 — 3,939 lines (35× median)
common/config.go:1 — 3,070 lines (27× median)
common/build.go:1 — 2,464 lines (22× median)
shells/abstract.go:1 — 2,180 lines (19× median)
executors/docker/docker.go:1 — 2,102 lines (18× median)

Engineering Process & SDLC Maturity

strong

No finding.

Product & Engineering Maturity

adequate
04.3

103 direct dependencies in a single manifest

adequate

go.mod declares 103 direct dependencies. Each one is a maintenance obligation, a supply-chain surface and a potential licence question that transfers with the asset. The count says nothing about whether any given dependency was a good choice; it says how many such choices a buyer inherits.

Evidence
go.mod — 103 declared
helpers/runner_wrapper/api/go.mod — 5 declared
04.62

Releases are cut from another branch than the one surveyed

adequate

The newest release, v19.4.1, is not on the branch this survey read; the newest release on it is v18.3.0. The shipped product may differ from what this report describes. Survey the release branch too.

Evidence
tag v19.4.1

Security & Reliability Posture

adequate
05.6

2 Dockerfiles run 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
dockerfiles/runner-helper/Dockerfile — runs as root
dockerfiles/runner/Dockerfile — runs as root
05.25

1 environment file is committed

adequate

.env is tracked in git. Environment files are where credentials usually live, and committing one usually means nobody decided how secrets reach the running application. Whatever is in it is in the history for good. Check 05.1 says whether it holds anything credential-shaped.

Evidence
.env — committed environment file
05.26

1 locked dependency has published vulnerabilities

adequate

1 of 298 locked dependencies match 1 published advisories in OSV. A lockfile says which version is installed, not whether the flawed code is reachable from this product, so each needs a look. Most are fixed by an upgrade, and the advisory names the version. This lockfile pins development tools alongside what ships and does not say which is which, so some of these may never reach a user.

Evidence
helpers/runner_wrapper/api/go.mod — golang.org/x/sys v0.42.0: GO-2026-5024 (unrated), fixed in 0.44.0

Observability & Operations

strong
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

Fit with the Acquirer

not assessable

Not rated: structurally not assessable from a repository.

Read more, or read your own

The full report on gitlab.com/gitlab-org/gitlab-runner: 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.