Read 2026-11-03
concourse/concourse: technical due diligence, read from its repository
What Borehole read in concourse/concourse's code and history at 352512d: 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 | adequate |
| Security & Reliability Posture | adequate |
| Observability & Operations | adequate |
| Fit with the Acquirer | not assessable |
What the repository says
- Releases are cut from another branch than the one surveyed
CONTRIBUTING.md:109: names Linux Foundation
Architecture & Codebase — including AI provenance
strongCommit messages are templated rather than written
adequate40% of commit subjects are exact repeats of another subject, and subject length varies by only 18.1 characters. A log written by someone explaining their reasoning to a future reader does not look like this. The log is therefore weak evidence of intent, whatever the code is like.
| 1714× 'bump atc' |
| 272× 'auto-bump' |
| 261× 'bump fly' |
atc/db/build.go is 2,294 lines, 29× this codebase's median file
adequateThe median source file here is 78 lines. 18 files exceed 1,000 lines, the largest being 2,294. 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.
atc/db/build.go:1 — 2,294 lines (29× median) |
atc/atccmd/command.go:1 — 2,244 lines (28× median) |
web/elm/src/Resource/Resource.elm:1 — 2,222 lines (28× median) |
atc/db/team.go:1 — 1,927 lines (24× median) |
web/elm/src/Dashboard/Dashboard.elm:1 — 1,675 lines (21× median) |
Engineering Process & SDLC Maturity
strongNo finding.
Product & Engineering Maturity
adequate108 direct dependencies in a single manifest
adequatego.mod declares 108 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.
go.mod — 108 declared |
web/wats/package.json — 5 declared |
package.json — 2 declared |
Releases are cut from another branch than the one surveyed
adequateThe newest release, v8.3.3, is not on the branch this survey read; the newest release on it is v8.3.0. The shipped product may differ from what this report describes. Survey the release branch too.
| tag v8.3.3 |
Security & Reliability Posture
adequate1 Dockerfile runs the application as root
adequateNo 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.
Dockerfile — runs as root |
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.
.env — committed environment file |
5 outbound calls can wait forever
adequate5 HTTP calls use a client with no timeout (Python `requests` without `timeout=`, or Go's default client). When a dependency slows down, each one holds a worker until the connection gives up, and enough of them take the service down with the dependency.
atc/atccmd/command.go:784 — outbound call without a timeout |
atc/policy/opa/opa.go:59 — outbound call without a timeout |
fly/commands/logout.go:76 — outbound call without a timeout |
6 SQL statements built from strings
adequate6 places in product code build SQL by formatting or joining strings rather than passing parameters. In each, what the code shows going in is a table or column name, a constant, or something the line does not show, not a request's value. Ask whether any value reaches these strings, rather than a parameter.
atc/db/build_being_watched_marker.go:71 — SQL built from a string |
atc/db/listener.go:133 — SQL built from a string |
atc/db/pipeline_lifecycle.go:144 — SQL built from a string |
54 locked dependencies have published vulnerabilities, 2 high or critical in what ships
adequate54 of 991 locked dependencies match 159 published advisories in OSV, 89 of them rated high or critical. 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.
1 workload setting can give a container the host, behind a chart value or in a stack built from source
adequate1 places run a container privileged or in the host's namespaces only when a Helm value switches them on, or in a compose file that builds the product from this repository, which is how it is developed rather than how it ships. Neither is on by default in what ships. Ask whether production sets the value or runs that stack.
docker-compose.yml:59 — host access behind a setting or in a local stack |
6 advisories against this project in the last 24 months
adequateThe newest was published on 2026-10-02. 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 3 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 8.3.0. Answer lives in: the release you run, set against each fixed version. The record is incomplete: NVD: 5 records name concourse with nothing tying them to this repository (CVE-2018-15798, CVE-2019-3792, CVE-2019-3803, …).
| 2026-10-02: GHSA-fcx6-pj3r-frxv (moderate), fixed in >= 8.3.1: load_var step can read any file on the Worker |
| 2026-10-02: GHSA-r298-g5jj-c9w4 (low), fixed in >= 8.3.1: Cache leak of IDToken var source to other pipelines or teams |
| 2026-08-17: GHSA-hg62-49fv-33pp (moderate), fixed in 8.3.0: DOS via HeartbeatWorker endpoint |
| 2026-08-17: GHSA-2w8g-h943-5fqh (low), fixed in 8.3.0: User with Worker's team private key can land/retire other team's workers |
| 2026-08-03: GHSA-vc3v-p3pr-4f5x (low), fixed in >= 8.2.5: Path traversal during secrets lookup |
Observability & Operations
adequateNo error reporter is wired in
adequateNothing 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.
| no error reporter initialised |
Has a reporting host, telemetry.concourse-ci.org; its default could not be read
adequateatc/atccmd/command.go names telemetry.concourse-ci.org as a place to report to, and no setting read here shows whether reporting is on as shipped. For a buyer running it inside their own product, ask whether copies report by default, what is sent, how often, and whether the buyer's customers were told.
atc/atccmd/command.go:782 — names telemetry.concourse-ci.org |
Fit with the Acquirer
not assessableNot rated: structurally not assessable from a repository.
Read more, or read your own
The full report on concourse/concourse: 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.