3b08cd7 · 2,018 commits · 130 files
Issued 2026-09-23
Nothing significant. Questions worth asking about Observability & Operations, Architecture & Codebase — including AI provenance.
35 checks ran across 6 assessable dimensions. None found a significant problem; 4 raised something worth a question. 5 findings, each with evidence. One dimension cannot be assessed without an acquirer.
- Words about people are today's: bands rather than exact shares, dates or day counts, and what the history measured rather than why.
- 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 | adequate | |
| 02 | Engineering Process & SDLC Maturity | strong | |
| 03 | Organization & Key-Person Risk | adequate | |
| 04 | Product & Engineering Maturity | adequate | |
| 05 | Security & Reliability Posture | strong | |
| 06 | Observability & Operations | adequate | |
| 07 | Fit with the Acquirer | not assessable |
- 23% of non-merge commits carry any trailer at all
- low trailer coverage: the convention may not be in consistent use
- no widespread author/committer date divergence
- deep scan blamed 128 of 128 counted files
Architecture & Codebase — including AI provenance
01 · adequate · ratings ↑context_test.go is 4,034 lines, 55× this codebase's median file
adequateThe median source file here is 73 lines. 6 files exceed 1,000 lines, the largest being 4,034. 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.
| line-count | context_test.go:1 — 4,034 lines (55× median) |
| line-count | context.go:1 — 1,545 lines (21× median) |
| line-count | binding/binding_test.go:1 — 1,435 lines (19× median) |
| line-count | gin_test.go:1 — 1,198 lines (16× median) |
| line-count | binding/form_mapping_test.go:1 — 1,147 lines (15× 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. 7 checks ran and none fired; the rejection log below says why each did not.
Organization & Key-Person Risk
03 · adequate · ratings ↑80% of contributors committed exactly once and never returned
adequate439 of 548 contributors made a single commit. That is the signature of a codebase that is hard to join: people arrive, land one change and do not come back. It matters after an acquisition because putting new engineers on this system is the first thing anyone will try to do.
| one-commit-authors | 439 of 548 authors (80.1%) have exactly one commit |
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.
Product & Engineering Maturity
04 · adequate · ratings ↑Change keeps returning to the same few files
adequateFive files out of 265 absorb 31% of all file-level change. Concentration like this is where debt is usually being serviced rather than repaid: the same code is reopened because it is load-bearing, fragile, or both. A repository cannot tell you which — that is a conversation with the team.
| touch-count | README.md — 339 commits touched it |
| touch-count | context.go — 291 commits touched it |
| touch-count | gin.go — 233 commits touched it |
| touch-count | context_test.go — 220 commits touched it |
| touch-count | go.mod — 154 commits touched it |
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 · strong · ratings ↑No finding. 10 checks ran and none fired; the rejection log below says why each did not.
Observability & Operations
06 · adequate · ratings ↑No telemetry or error reporting is wired in anywhere
adequateNone of 123 readable files references an instrumentation, metrics or error-reporting library. If this system is in production, nobody learns that it broke from the system itself — they learn it from a customer. That is a reliability finding before it is an observability one.
| telemetry-scan | searched 123 tracked text files for 15 known instrumentation libraries; 0 matched |
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.
No structured logging library is in use
adequateNothing 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.
| logging-scan | searched 123 files for 10 structured logging libraries; 0 matched |
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
3 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.
Engineering Process & SDLC Maturity
02 · high coverage- Incident response practice is not visible in a repository.
Organization & Key-Person Risk
03 · partial coverage- Hiring pipeline, bench depth and retention are not visible in a repository.
- Whether the dominant contributor is part of the transaction.
- Seniority, levelling and who actually mentors whom.
- Whether the team wants to stay after the deal closes.
Product & Engineering Maturity
04 · minimal coverage- Roadmap credibility requires the data room.
- Whether technical debt is acknowledged and funded.
Security & Reliability Posture
05 · partial coverage- Incident history and failure-mode analysis are not in the repository.
Observability & Operations
06 · partial coverage- Whether anyone watches the telemetry that exists.
Fit with the Acquirer
07 · none coverageNot rated: structurally not assessable from a repository.
- This is a Go codebase. Does your engineering organisation already run Go in production, or would this be the first?
- 548 people have committed here. Which of them are you acquiring, and which are you replacing?
- The bulk of this system sits in binding/, docs/, examples/. Which of your existing systems would each of those have to absorb or replace?
- There is no deployment configuration in the repository. Where does this actually run today, and who owns that environment?
- 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?
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/gin-gonic/gin/3b08cd7)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.
- 1bd0ecf 2026-10-04 · strong
Rejection log — 30 signals that ran and did not fire
Appendix: rejection log — 30 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 — 26
| Signal | What it found |
|---|---|
| 04.debt_markers | debt markers are sparsemarkers 9 · per kloc 0.31 · lines read 29,279 |
| 04.dependency_sprawl | direct dependency counts are unremarkable |
| 04.test_growth | test effort kept pace with code writtenlate test per code 0.698 · early test per code 0.544 |
| 04.churn_trend | rework is not rising against new worklate delete per insert 0.551 · early delete per insert 0.56 |
| 03.contributor_concentration | no single contributor dominates the historyauthors 548 · top share less than a quarter · bus factor 5 |
| 03.active_contributors | more than one contributor active in the trailing yearall time 548 · active 12mo 57 |
| 03.knowledge_silos | every substantial directory has been touched by more than one personauthors 548 · directories 5 |
| 03.contributor_attrition | no contributor dominates enough for their absence to matterauthors 548 · top share less than a quarter · top contributor last committed more than three years ago |
| 02.merge_discipline | a meaningful share of change arrives through a reviewable pathmerges 216 · commits 2,018 · reviewed share 0.671 |
| 02.ci_presence | CI configuration is present in the working treecount 4 |
| 02.test_presence | tests are present in a normal proportion to sourcetests 41 · source 99 · test ratio 0.414 |
| 02.release_cadence | tags are presenttags 38 |
| 02.conventional_commits | commit subjects generally carry contentsampled 1,802 · low content share 0.012 |
| 02.branch_protection_hints | process scaffolding is present in the repository |
| 02.ci_runs_tests | CI invokes a test runnerconfigs 4 · with tests 1 |
| 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 965 · share of insertions 0.0149 |
| 01.message_uniformity | commit subjects vary in wording and lengthlength stdev 19.91 · repeat share 0.036 |
| 01.revision_depth | most files were revisited after they were first writtenfiles seen 265 · write once share 0.185 |
| 01.duplicated_blocks | little shipping code is repeated verbatim across filesshare 0.0025 · product files 98 · distinct blocks 16,232 |
| 05.committed_secrets | no credential-shaped strings outside test and fixture pathsnote the working tree only; history is scanned at --deep · patterns 7 · files read 123 |
| 05.security_guardrails | at least one standard guard rail is configured |
| 05.license_present | a licence file is presentfound True |
| 05.secrets_in_history | no credential-shaped string was ever added outside test and fixture pathspatterns 7 · truncated False · added lines 56,689 |
| 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 |
Could not conclude, or did not apply — 4
Not a clean result. Each says why it could not answer here.
| Signal | Why |
|---|---|
| 05.dependency_pinning | no manifest whose pinning can be read without a lockfile |
| 05.container_runs_as_root | no Dockerfile to read |
| 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 |
Anyone can check this report against the authoritative record — click the stamp, or enter ZHCG-7NFS-P8RB at borehole.dev/verify.
The code commits to the 36 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/ZHCG7NFSP8RB?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-09-23 · shown | borehole 0.1.0.dev0 | 6 | adequate |
3 other readings (show)
| 2026-09-24 | borehole 0.4.0 | 4 | adequate |
| 2026-09-24 | borehole 0.4.0.dev2 | 3 | adequate |
| 2026-09-24 | borehole 0.4.0.dev1 | 3 | adequate |
What this scan did with the repository — 5 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.5s | read repository metadata from the GitHub API | size mb: 10.4authenticated: False |
| 2.3s | cloned the repository to a temporary directory | depth: full |
| 2.9s | read the git history | commits: 2018tracked files: 130 |
| 7.1s | ran the deterministic checks | blame pass: Trueread working tree: True |
| 7.1s | deleting the working copy |
Total 7.1s ·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).