0e3fe7d · 15,564 commits · 1,444 files
Issued 2026-10-04
Reads strong: 4 of 6 rated dimensions are strong, 2 are adequate and none is significant.
105 checks ran across 6 assessable dimensions. Security & Reliability Posture and Product & Engineering Maturity are adequate. 7 findings, each with evidence. One dimension cannot be assessed without an acquirer.
This repository reads strong. Show it in your README: the badge links to a page where anyone can check the reading. If you embed it: link it to the report, remove it if the report is delisted, and do not present it as a certification or an endorsement.
[](https://borehole.dev/verify/4MW8GV0VAMKZ?via=badge)- 04.62 Releases are cut from another branch than the one surveyed
- 1 finding from checks Borehole's calibration found wrong more often than right is no longer published.
| Dimension | Rating | ||
|---|---|---|---|
| 01 | Architecture & Codebase — including AI provenance | strong | |
| 02 | Engineering Process & SDLC Maturity | strong | |
| 03 | Organization & Key-Person Risk | strong | |
| 04 | Product & Engineering Maturity | adequate | |
| 05 | Security & Reliability Posture | adequate | |
| 06 | Observability & Operations | strong | |
| 07 | Fit with the Acquirer | not assessable |
- 3% of non-merge commits carry any trailer at all
- low trailer coverage: the convention may not be in consistent use
- 27% of commits show author/committer date divergence, which is the shape of replayed history that can drop trailers
- deep scan blamed 1,430 of 1,430 counted files
Architecture & Codebase — including AI provenance
01 · strong · ratings ↑executors/kubernetes/kubernetes.go is 3,939 lines, 35× this codebase's median file
adequateThe 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.
A note that does not affect this rating: measured against its own codebase's median, it is below the 85th percentile of 382 surveyed projects' largest files, where this check begins to count.
| line-count | executors/kubernetes/kubernetes.go:1 — 3,939 lines (35× median) |
| line-count | common/config.go:1 — 3,070 lines (27× median) |
| line-count | common/build.go:1 — 2,464 lines (22× median) |
| line-count | shells/abstract.go:1 — 2,180 lines (19× median) |
| line-count | executors/docker/docker.go:1 — 2,102 lines (18× median) |
Respond to this finding
Your response is published beside the finding, not instead of it. A finding you can argue with is the point — and a wrong one is calibration data we want.
An owner's response is removed only when it is unlawful, impersonates someone, publishes personal data or a credential, or is not about the finding. Disagreeing with the report is never a reason. To report a response, or to reach us about one, write to takedown@borehole.dev.
Engineering Process & SDLC Maturity
02 · strong · ratings ↑No finding. 16 checks ran and none fired; the rejection log below says why each did not.
Organization & Key-Person Risk
03 · strong · ratings ↑No finding. 10 checks ran and none fired; the rejection log below says why each did not.
Product & Engineering Maturity
04 · adequate · ratings ↑103 direct dependencies in a single manifest
adequatego.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.
| direct-dependencies | go.mod — 103 declared |
| direct-dependencies | helpers/runner_wrapper/api/go.mod — 5 declared |
Respond to this finding
Your response is published beside the finding, not instead of it. A finding you can argue with is the point — and a wrong one is calibration data we want.
An owner's response is removed only when it is unlawful, impersonates someone, publishes personal data or a credential, or is not about the finding. Disagreeing with the report is never a reason. To report a response, or to reach us about one, write to takedown@borehole.dev.
Releases are cut from another branch than the one surveyed
adequateThe 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.
A note that does not affect this rating: notes like it are common in well-run projects.
| 3c39fcebf | tag v19.4.1 |
Respond to this finding
Your response is published beside the finding, not instead of it. A finding you can argue with is the point — and a wrong one is calibration data we want.
An owner's response is removed only when it is unlawful, impersonates someone, publishes personal data or a credential, or is not about the finding. Disagreeing with the report is never a reason. To report a response, or to reach us about one, write to takedown@borehole.dev.
Security & Reliability Posture
05 · adequate · ratings ↑2 Dockerfiles run 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.
| no-USER-instruction | dockerfiles/runner-helper/Dockerfile — runs as root |
| no-USER-instruction | dockerfiles/runner/Dockerfile — runs as root |
Respond to this finding
Your response is published beside the finding, not instead of it. A finding you can argue with is the point — and a wrong one is calibration data we want.
An owner's response is removed only when it is unlawful, impersonates someone, publishes personal data or a credential, or is not about the finding. Disagreeing with the report is never a reason. To report a response, or to reach us about one, write to takedown@borehole.dev.
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.
A note that does not affect this rating: in Borehole's calibration, this check's notes were usually true but overstated.
| .env | .env — committed environment file |
Respond to this finding
Your response is published beside the finding, not instead of it. A finding you can argue with is the point — and a wrong one is calibration data we want.
An owner's response is removed only when it is unlawful, impersonates someone, publishes personal data or a credential, or is not about the finding. Disagreeing with the report is never a reason. To report a response, or to reach us about one, write to takedown@borehole.dev.
1 locked dependency has published vulnerabilities
adequate1 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.
A note that does not affect this rating: in Borehole's calibration, this check's notes were usually true but overstated.
| helpers/runner_wrapper/api/go.mod | helpers/runner_wrapper/api/go.mod — golang.org/x/sys v0.42.0: GO-2026-5024 (unrated), fixed in 0.44.0 |
Respond to this finding
Your response is published beside the finding, not instead of it. A finding you can argue with is the point — and a wrong one is calibration data we want.
An owner's response is removed only when it is unlawful, impersonates someone, publishes personal data or a credential, or is not about the finding. Disagreeing with the report is never a reason. To report a response, or to reach us about one, write to takedown@borehole.dev.
Observability & Operations
06 · strong · ratings ↑No 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.
A note that does not affect this rating: notes like it are common in well-run projects.
| error reporting | no error reporter initialised |
Respond to this finding
Your response is published beside the finding, not instead of it. A finding you can argue with is the point — and a wrong one is calibration data we want.
An owner's response is removed only when it is unlawful, impersonates someone, publishes personal data or a credential, or is not about the finding. Disagreeing with the report is never a reason. To report a response, or to reach us about one, write to takedown@borehole.dev.
Fit with the Acquirer
07 · not assessable · ratings ↑Not rated: structurally not assessable from a repository. What a person adds here.
Check it on the running system
5 checks against the running system follow from the findings above: what a buyer's engineer will try, how to run it first, and what to have ready. A paid survey of this repository includes them.
A paid survey of a public repository is also reviewed: a language model reads each finding against the code and withdraws only findings it judges the code contradicts, each listed with its reason. The review is a language model's reading of the findings against the code, and it can be wrong. It never adds a finding, never raises a band, and never removes a finding from a proven check or an advisory that affects the surveyed version.
What a person adds
The survey reads what the repository can show. The code cannot settle these questions, and on them this report states nothing. Each says where its answer lives: your own engineer, the company, or an assessor you choose can settle it. Questions marked measured open with something this repository shows.
Architecture & Codebase — including AI provenance
01 · full coverage- measured No architecture or design document is in the tree, across 701 product files. Where does the design live, and who holds it?
- Is the architecture right for the next three years of the product?
- Were the home-grown components reasonable choices when they were made, and are they now?
Engineering Process & SDLC Maturity
02 · high coverage- Is review real or a rubber stamp? Comment depth and time to approve need the pull request history.
- Is delivery planned and measured, or heroic?
- How are incidents run, reviewed and learned from?
Organization & Key-Person Risk
03 · partial coverage- measured 971 people have committed here. Which of them are you acquiring, and which are you replacing?
- Who mentors whom, and would that survive a departure?
- Can the team grow, and who stands behind the top three contributors?
- Is the seniority mix sound, and will pay survive your salary bands?
- Is the pace sustainable? Commit times cannot say: git keeps no reliable local time.
- Does the team want to stay after close?
- How are decisions made and disagreements resolved?
Product & Engineering Maturity
04 · minimal coverage- Can this team deliver the stated roadmap on the stated timeline?
- Does leadership know about the debt, and is time budgeted to repay it?
- Is the engineering shape consistent with the commercial story?
Security & Reliability Posture
05 · partial coverage- measured 05.5 found credential-shaped strings in this repository. Was each one revoked at the provider? Deleting it from the code revokes nothing; only the provider's audit log shows that it was.
- measured No threat model is in the tree of what looks like a running service. Does one exist elsewhere, and who owns it?
- What has actually broken, how often, and how badly?
- What did external testing find, and was it fixed?
- What is the SOC 2, ISO 27001 or GDPR status, and where is the evidence?
Observability & Operations
06 · partial coverage- measured Nothing in the tree backs up or restores data. How is data backed up, and has a restore ever been rehearsed?
- measured No alert rule is defined in the repository. Where are alerts defined, who receives them, and when did one last fire?
- Are the dashboards opened, the alerts acknowledged and the pages answered?
- Are the service-level objectives actually met?
- Who carries the pager, and how often does it go off?
- What does it cost to run, and how much headroom is there?
Fit with the Acquirer
07 · none coverageNot rated: structurally not assessable from a repository.
- This is primarily a Go codebase. Does your engineering organisation already run Go in production, or would this be the first?
- The bulk of this system sits in executors/, helpers/, docs-locale/. Which of your existing systems would each of those have to absorb or replace?
- The repository carries deployment configuration (Procfile and 3 more). Does that match your deployment and on-call model, or does it need rehosting first?
- What is your tolerance for the findings above remaining unaddressed for the first two quarters after close, given everything else that will compete for this team's time?
- Which of these systems duplicate yours, and which get retired?
- What will integration cost, and in what order?
- Where does the team land in your organisation, and who reports to whom?
- Are there earn-outs, retention packages or contractor IP to assign?
- Do customer contracts limit hosting, regions or vendors?
A human assessment is Borehole's own paid service, €12,000+ (total price is determined per engagement; travel billed at cost). It is not independent of this report: the same business produced both. It is a separate contract, with its own scope, terms and reliance.
Embed the badge
Tied to this commit and this date, and it fades after 90 days — an honest badge is one that expires. A repository with significant findings gets a neutral "read" badge rather than a red one: the library is where the range is visible, not someone else's README.
[](/r/gitlab.com/gitlab-org+gitlab-runner/0e3fe7d)If you embed it: link it to the report, remove it if the report is delisted, and do not present it as a certification or an endorsement.
Rejection log — 98 signals that ran and did not fire
Appendix: rejection log — 98 signals that ran and did not fire
Published on purpose. A signal that looked and decided not to fire has told you something, and this is the calibration data behind every threshold above.
Looked, and found nothing — 77
| Signal | What it found |
|---|---|
| 04.hotspot_concentration | change is spread across the codebase rather than pooling in a few filesfiles 31,637 · top5 share 0.025 |
| 04.debt_markers | debt markers are sparsemarkers 35 · per kloc 0.1 · lines read 347,346 |
| 04.test_growth | test effort kept pace with code writtenlate test per code 2.195 · early test per code 0.216 |
| 04.churn_trend | rework is not rising against new worklate delete per insert 0.42 · early delete per insert 0.217 |
| 04.fixes_with_tests | fixes usually come with a testfixes 290 · share 0.4 · with tests 116 |
| 04.fix_share_trend | fixing is not crowding out building |
| 04.compat_layers | little code is kept for the old wayshare 0.0 · code files 474 · compat files 0 |
| 06.telemetry_presence | a telemetry or error-reporting library is referencednote presence only; whether anyone watches it is not visible here · matches 24 |
| 06.structured_logging | a structured logging library is referencedmatches 211 |
| 06.healthcheck_presence | a health or readiness check is defined |
| 06.telemetry_depth | the service is visible in more than one way |
| 06.print_logging | raw prints are few, or outnumbered by logger callsprints 22 · logger calls 168 |
| 06.correlation_ids | a request can be followed through the logstracing True · request id sites 10 |
| 06.usage_reporting_default | the product's code names no reporting hostsettings on 0 · settings off 0 |
| 06.environment_branching | environment differences live in configurationsites 0 |
| 06.release_markers | releases are markedtags last year 43 · release commits 11 · changelog commits 59 |
| 06.migrate_on_start | migrations do not run at container start |
| 03.contributor_concentration | no single contributor dominates the last 24 monthsyears 12.2 · window last 24 months · authors 971 |
| 03.active_contributors | more than one contributor active in the trailing yearall time 971 · active 12mo 134 |
| 03.knowledge_silos | every substantial directory has been touched by more than one personauthors 971 · directories 17 |
| 03.drive_by_contributors | an open contributor base, where one-commit contributors are normalauthors 971 · one off share 0.572 |
| 03.contributor_attrition | no contributor dominates enough for their absence to matterauthors 971 · top share less than a quarter · top contributor last committed within the last three months |
| 03.critical_path_ownership | more than one person changes the critical pathsauthors 233 |
| 03.second_contributor_attrition | the second and third contributors are still active |
| 03.bus_factor_trend | the team has not narrowed to one person |
| 03.joiners_and_leavers | the team is not shrinkingleft 12 · joined 27 · regular last year 44 |
| 02.merge_discipline | a meaningful share of recent change carries evidence of reviewmerges 1,601 · window last 24 months · with tracked 285 |
| 02.ci_presence | CI configuration is present in the working treecount 18 |
| 02.test_presence | tests are present in a normal proportion to sourcetests 465 · source 930 · test ratio 0.5 |
| 02.release_cadence | tags are presenttags 533 |
| 02.conventional_commits | commit subjects generally carry contentsampled 9,947 · low content share 0.013 |
| 02.branch_protection_hints | process scaffolding is present in the repository |
| 02.ci_runs_tests | CI invokes a test runnerconfigs 18 · with tests 2 |
| 02.skipped_tests | few tests are switched offfocused 0 · skipped 0 · test files 504 |
| 02.ci_test_gating | no test run in CI is written so that it cannot failconfigs 18 |
| 02.revert_share | change is rarely undoneshare 0.009 · reverts 18 · recent commits 2,048 |
| 02.dependency_update_cadence | dependencies move with the codelockfiles 3 · commits since 3 · days since lockfile changed 1 |
| 02.flaky_test_markers | tests are not retried until they passtest retries 0 · suite retries 0 |
| 02.lint_in_build | a linter or formatter runs in the buildwired 2 · ci configs 18 · product files 474 |
| 02.long_lived_branches | the typical branch reaches the trunk quicklyshare 0.032 · merges 1,509 · long lived 48 |
| 02.commit_size | changes arrive in reviewable sizesshare 0.008 · commits 1,824 · over 2000 lines 15 |
| 01.burst_import | no commit run met both the rate and the net-addition thresholdgap seconds 180 · min add ratio 3.0 · min net added 2,000 |
| 01.initial_dump | first commit is not a disproportionate share of the codebaseinsertions 19 · share of insertions 0.0 |
| 01.message_uniformity | commit subjects vary in wording and lengthlength stdev 19.52 · repeat share 0.088 |
| 01.revision_depth | most files were revisited after they were first writtenfiles seen 681 · write once share 0.229 |
| 01.duplicated_blocks | little shipping code is repeated verbatim across filesshare 0.0043 · product files 465 · distinct blocks 51,482 |
| 01.swallowed_errors | errors are rarely thrown awayloc 348,703 · files 0 · per kloc 0.0 |
| 01.build_reproducibility | every base image names a versionfloating 0 · from lines 2 |
| 01.unfinished_migration | no language migration is stalled halfway |
| 01.weights_in_git | no model weights are committedfiles 0 |
| 05.committed_secrets | no credential-shaped strings outside test and fixture pathsnote the working tree only; the history is 05.5 · patterns 8 · files read 1,362 |
| 05.security_guardrails | at least one standard guard rail is configured |
| 05.license_present | a licence file is presentfound True |
| 05.outbound_timeouts | outbound calls set timeouts, or are fewcalls without timeout 1 |
| 05.sql_from_strings | no SQL is assembled from strings in product codefiles 0 · sites 0 · value interpolated 0 |
| 05.shell_from_strings | product code does not build shell commands from stringssites 0 |
| 05.unsafe_deserialization | no code-executing deserialiser in product codesites 0 |
| 05.tls_verification_off | no TLS verification is switched off in product codefiles 0 · sites 0 · pinned instead 0 |
| 05.privileged_workloads | no workload runs privileged or in the host's namespacessites 0 · behind a setting or built here 0 |
| 05.credentials_in_deploy_config | deployment configuration references secrets, never holds themfiles 0 · sites 0 |
| 05.signing_material | no signing keystore or profile is committedfiles 0 |
| 05.license_vendored_unlicensed | no vendored third-party code is committedcomponents 0 |
| 05.license_grant_unclear | the licence is recognisable as MITclass permissive · license MIT |
| 05.committed_native_libraries | no widely used compiled library is committed to the productlibraries 0 |
| 04.api_versions_coexisting | one API version is served, or none |
| 04.deprecations_lingering | few deprecations have outlived two yearsolder than two years 1 · files with deprecations 140 |
| 04.dependency_churn | few dependencies were added and dropped within 60 daysdependencies seen 401 · added in two years 108 · removed within 60 days 2 |
| 04.ci_platforms_dropped | no platform was dropped from CI in the last two years |
| 04.repository_status | the README's first screen states no end, move or freezestatements 0 |
| 02.development_elsewhere | nothing says development happens elsewhereno pr statements 0 · mirror statements 0 · replayed commit share 0.0 |
| 05.licence_changes | the root licence has not changed in the history readlicence versions 1 · unreleased changes 0 |
| 05.paid_edition | no directory carries a separate paid-edition licencedirectories 0 |
| 04.releases_stopped | releases keep pace with developmentmedian gap days 0.0 · days since last tag 1 · commits last 90 days 878 |
| 03.single_maintainer | no file says one person maintains itstatements 0 |
| 05.project_advisories | no published advisory affects the surveyed versionaffecting 0 · exploited 0 · advisories 0 |
| 05.advisory_record | no advisory against the project in the last 24 monthscritical 0 · affecting 0 · could not tell 0 |
| 05.project_exploited | no affecting advisory is on CISA's Known Exploited listexploited 0 |
Could not conclude, or did not apply — 21
Not a clean result. Each says why it could not answer here.
| Signal | Why |
|---|---|
| 04.eol_runtime | no pinned runtime version to check |
| 04.schema_churn | no schema migrations to read |
| 04.dependency_redundancy | no JavaScript manifest to read |
| 06.alert_rules | no alert rules in the repository; they may live in a console |
| 06.deployed_image_floats | no deployment descriptor names an image |
| 06.probes_identical | no Kubernetes probes |
| 06.single_replica | no Kubernetes deployments |
| 06.feature_flags | no feature-flag service; flags may live elsewhere |
| 01.notebook_outputs | not a data or machine-learning repository |
| 05.dependency_pinning | no manifest whose pinning can be read without a lockfile |
| 05.supply_chain_pinning | no CI actions or pipe-to-shell installs to check |
| 05.migration_reversibility | too few migrations to judge |
| 05.resource_limits | no Kubernetes workload manifests |
| 05.public_env_secret | not a frontend |
| 05.unsafe_html | not a frontend |
| 05.source_maps_shipped | not a frontend |
| 05.cleartext_traffic | not a mobile app |
| 05.dataset_provenance | not a data or machine-learning repository |
| 05.license_copyleft_inherited | no third-party code is committed to this repository, so the licences it depends on are resolved at build time and are not readable here |
| 05.license_manifest_conflict | no packaging manifest states a licence |
| 04.flags_accumulating | few or no feature flags in the history |
Anyone can check this report against the authoritative record — click the stamp, or enter 4MW8-GV0V-AMKZ at borehole.dev/verify.
The code commits to the 106 checks this run performed, the bands they produced, and the commit they were read at. It does not cover checks written since.
Put the mark in your README
The image is wrapped in a link to the verification page, so a reader can check it rather than take it on trust. If you embed it: link it to the report, remove it if the report is delisted, and do not present it as a certification or an endorsement.
[](https://borehole.dev/verify/4MW8GV0VAMKZ?via=badge)
A survey is a reading by a particular version of the assessor. Older readings are kept rather than replaced, because a verification mark attests to the survey it was issued for — overwriting one would make every code already in circulation read as tampered.
| Read | Assessor | Findings | Band |
|---|---|---|---|
| 2026-10-04 · shown | borehole 0.7.13 | 8 | strong |
8 earlier (show)
| 2026-10-03 | borehole 0.7.12 | 8 | strong |
| 2026-10-03 | borehole 0.7.11 | 8 | strong |
| 2026-10-02 | borehole 0.7.10 | 8 | strong |
| 2026-10-01 | borehole 0.7.9 | 8 | adequate |
| 2026-09-30 | borehole 0.7.8 | 8 | adequate |
| 2026-09-29 | borehole 0.7.6 | 8 | adequate |
| 2026-09-28 | borehole 0.7.5 | 8 | adequate |
| 2026-09-28 | borehole 0.7.4 | 8 | adequate |
Where this scan ran
This scan ran on ordinary cloud infrastructure (cloud-run), not in a hardware-isolated confidential VM. Nothing about it is attested by Google.
What an attested survey proves, and what it does not.
What this scan did with the repository — 3 steps
Written by the steps themselves as they ran, not described afterwards. A hand-written account of a data flow drifts the first time somebody changes the flow and not the account.
| At | Step | Detail |
|---|---|---|
| 0.0s | re-read from the facts kept at the last survey; nothing was cloned | facts version: 1d7c04ef8dca7905 |
| 9.6s | ran the deterministic checks | blame pass: Trueread working tree: False |
| 9.6s | recorded where this scan ran | attested: Falseenvironment: cloud-run |
Total 9.6s ·source content sent off this machine: none · calls to a language model: 0 · the clone was deleted when the survey ended
An automated reading of a repository's code and its history up to one commit, with public advisory records. It may be wrong, it is not legal, financial, investment or security advice, and it does not replace diligence by a qualified person. It is provided for information: nobody may rely on it (Borehole's terms, section 3).