e4c0f1f · 352 commits · 86 files
Issued 2026-09-27
Nothing significant. Questions worth asking about Organization & Key-Person Risk, Security & Reliability Posture.
100 checks ran across 6 assessable dimensions. 1 finding is worth checking first. 7 findings, each with evidence. One dimension cannot be assessed without an acquirer.
Borehole's proprietary scoring is calibrated across hundreds of repositories. Each finding here reads significant, but its check has not yet held up often enough in that calibration to rate significant on its own. If one holds when someone checks it, it is significant.
- 05.26 8 locked dependencies have published vulnerabilities, 16 high or critical
- 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 rated significant by a check that has not yet held up in Borehole's calibration is now worth checking first.
- 3 findings from checks Borehole's calibration found wrong more often than right are no longer published.
| Dimension | Rating | ||
|---|---|---|---|
| 01 | Architecture & Codebase — including AI provenance | strong | |
| 02 | Engineering Process & SDLC Maturity | adequate | |
| 03 | Organization & Key-Person Risk | adequate | |
| 04 | Product & Engineering Maturity | not assessable | |
| 05 | Security & Reliability Posture | adequate | |
| 06 | Observability & Operations | adequate | |
| 07 | Fit with the Acquirer | not assessable |
- 45% 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 84 of 84 counted files
Architecture & Codebase — including AI provenance
01 · strong · ratings ↑No finding. 11 checks ran and none fired; the rejection log below says why each did not.
Engineering Process & SDLC Maturity
02 · adequate · ratings ↑Almost no process scaffolding exists in the repository
adequateOf 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.
| process-scaffolding | 1 of 5 markers present across 86 tracked files |
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.
Organization & Key-Person Risk
03 · adequate · ratings ↑73% of contributors committed exactly once and never returned
adequate24 of 33 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 | 24 of 33 authors (72.7%) 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.
The contributor who wrote a quarter or more of this has not committed here for more than two years
adequateOne person authored a quarter or more of 253 commits and has not committed here for more than two years, while the repository has kept moving. The concentration figure alone would not show this. Whoever is changing this code now is not the person who wrote most of it, which is the situation an acquirer is usually told they are avoiding. The history shows only that no commits of theirs landed here, not why.
| last-commit-by-top-author | last commit more than two years ago, measured to the survey |
| git shortlog -sn | top author a quarter or more of 253 commits |
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 · not assessable · ratings ↑Not rated: only 8 of 19 checks could reach a conclusion here; the rest do not apply to this repository or could not read it. What a person adds here.
Security & Reliability Posture
05 · adequate · ratings ↑1 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.
| no-USER-instruction | 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.
8 locked dependencies have published vulnerabilities, 16 high or critical
adequate worth checking first8 of 224 locked dependencies match 24 published advisories in OSV, 16 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.
The check that found this reads significant, but it has not yet held up often enough in Borehole's calibration to rate a finding significant on its own. Opening go.mod settles it. If it holds when someone checks it, this finding is significant.
| go.mod | go.mod — golang.org/x/crypto v0.47.0: GHSA-5cgq-3rg8-m6cv (critical), fixed in 0.52.0 |
| go.mod | go.mod — google.golang.org/grpc v1.75.0: GHSA-p77j-4mvh-x3m3 (critical), fixed in 1.79.3 |
| go.mod | go.mod — github.com/go-acme/lego/v4 v4.26.0: GHSA-qqx8-2xmm-jrv8 (high), fixed in 4.34.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 · adequate · ratings ↑One request cannot be followed through the logs
adequateNothing 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.
| request ids | no request id, correlation id or tracing found |
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 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.
| 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- 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 33 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 coverageNot rated: only 8 of 19 checks could reach a conclusion here; the rest do not apply to this repository or could not read it.
- 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 server/, cli/, config/. Which of your existing systems would each of those have to absorb or replace?
- The repository carries deployment configuration (Dockerfile). 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/codeberg.org/codeberg+pages-server/e4c0f1f)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 — 93 signals that ran and did not fire
Appendix: rejection log — 93 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 — 57
| Signal | What it found |
|---|---|
| 04.hotspot_concentration | change is spread across the codebase rather than pooling in a few filesfiles 142 · top5 share 0.231 |
| 04.debt_markers | debt markers are sparsemarkers 18 · per kloc 2.72 · lines read 6,627 |
| 04.dependency_sprawl | direct dependency counts are unremarkable |
| 04.churn_trend | rework is not rising against new worklate delete per insert 0.504 · early delete per insert 0.658 |
| 06.telemetry_presence | a telemetry or error-reporting library is referencednote presence only; whether anyone watches it is not visible here · matches 1 |
| 06.structured_logging | a structured logging library is referencedmatches 27 |
| 06.print_logging | raw prints are few, or outnumbered by logger callsprints 1 · logger calls 108 |
| 06.environment_branching | environment differences live in configurationsites 0 |
| 06.migrate_on_start | migrations do not run at container start |
| 03.contributor_concentration | no single contributor dominates the whole historyyears 5.5 · window whole history · authors 33 |
| 03.active_contributors | more than one contributor active in the trailing yearall time 33 · active 12mo 4 |
| 03.knowledge_silos | every substantial directory has been touched by more than one personauthors 33 · directories 3 |
| 03.critical_path_ownership | more than one person changes the critical pathsauthors 9 |
| 02.merge_discipline | a meaningful share of recent change carries evidence of reviewmerges 0 · window last 24 months · with tracked 4 |
| 02.ci_presence | CI configuration is present in the working treecount 2 |
| 02.test_presence | tests are present in a normal proportion to sourcetests 11 · source 48 · test ratio 0.229 |
| 02.release_cadence | tags are presenttags 36 |
| 02.conventional_commits | commit subjects generally carry contentsampled 342 · low content share 0.038 |
| 02.ci_runs_tests | CI invokes a test runnerconfigs 2 · with tests 1 |
| 02.skipped_tests | few tests are switched offfocused 0 · skipped 0 · test files 11 |
| 02.ci_test_gating | no test run in CI is written so that it cannot failconfigs 2 |
| 02.dependency_update_cadence | dependencies move with the codelockfiles 1 · commits since 1 · days since lockfile changed 132 |
| 02.flaky_test_markers | tests are not retried until they passtest retries 0 · suite retries 0 |
| 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 426 · share of insertions 0.0214 |
| 01.message_uniformity | commit subjects vary in wording and lengthlength stdev 21.73 · repeat share 0.006 |
| 01.revision_depth | most files were revisited after they were first writtenfiles seen 55 · write once share 0.236 |
| 01.oversized_modules | no module is an outlier against this codebase's own normlargest 663 · threshold 1,000 · median lines 72 |
| 01.duplicated_blocks | little shipping code is repeated verbatim across filesshare 0.0004 · product files 37 · distinct blocks 2,596 |
| 01.swallowed_errors | errors are rarely thrown awayloc 6,699 · 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 72 |
| 05.security_guardrails | at least one standard guard rail is configured |
| 05.license_present | a licence file is presentfound True |
| 05.secrets_management_pattern | no environment file is committed outside tests and examplesenv files 0 |
| 05.outbound_timeouts | outbound calls set timeouts, or are fewcalls without timeout 0 |
| 05.sql_from_strings | no SQL is assembled from strings in product codefiles 0 · sites 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 EPL-2.0class weak-copyleft · license EPL-2.0 |
| 04.dependency_churn | few dependencies were added and dropped within 60 daysdependencies seen 292 · added in two years 154 · removed within 60 days 10 |
| 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 |
| 05.paid_edition | no directory carries a separate paid-edition licencedirectories 0 |
| 04.releases_stopped | releases keep pace with developmentmedian gap days 55.0 · days since last tag 312 · commits last 90 days 1 |
| 04.release_branch | the newest release was cut from the branch surveyedelsewhere 8 · on branch 28 · tags in window 36 |
| 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.project_exploited | no affecting advisory is on CISA's Known Exploited listexploited 0 |
Could not conclude, or did not apply — 36
Not a clean result. Each says why it could not answer here.
| Signal | Why |
|---|---|
| 04.test_growth | not enough code written in either half to compare |
| 04.eol_runtime | no pinned runtime version to check |
| 04.fixes_with_tests | too few fixes in 24 months to judge |
| 04.fix_share_trend | fewer than six busy quarters to compare |
| 04.schema_churn | no schema migrations to read |
| 04.compat_layers | too little code |
| 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.release_markers | fewer than 100 commits in the last year |
| 06.feature_flags | no feature-flag service; flags may live elsewhere |
| 03.second_contributor_attrition | too little recent history |
| 03.bus_factor_trend | fewer than three active years to compare |
| 03.joiners_and_leavers | too few regular contributors to see a trend |
| 02.revert_share | too few recent commits to judge how often change is undone |
| 02.lint_in_build | too small, or no CI to wire a linter into (02.2) |
| 02.long_lived_branches | too few merges to judge (squash and rebase leave none) |
| 02.commit_size | too few recent commits |
| 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 |
| 04.api_versions_coexisting | one API version is served, or none |
| 04.deprecations_lingering | few deprecations have outlived two years |
| 04.ci_platforms_dropped | no platform was dropped from CI in the last two years |
Anyone can check this report against the authoritative record — click the stamp, or enter 7GCC-YZ4E-FBZ8 at borehole.dev/verify.
The code commits to the 103 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/7GCCYZ4EFBZ8?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-27 · shown | borehole 0.7.3 | 10 | adequate |
9 other readings (show)
| 2026-10-04 | borehole 0.7.13 | 10 | adequate |
| 2026-10-03 | borehole 0.7.12 | 10 | adequate |
| 2026-10-03 | borehole 0.7.11 | 10 | adequate |
| 2026-10-02 | borehole 0.7.10 | 10 | adequate |
| 2026-10-01 | borehole 0.7.9 | 10 | adequate |
| 2026-09-30 | borehole 0.7.8 | 11 | adequate |
| 2026-09-29 | borehole 0.7.6 | 11 | adequate |
| 2026-09-28 | borehole 0.7.5 | 11 | adequate |
| 2026-09-28 | borehole 0.7.4 | 11 | 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: aa57b0e0fea635c1 |
| 9.8s | ran the deterministic checks | blame pass: Trueread working tree: False |
| 9.8s | recorded where this scan ran | attested: Falseenvironment: cloud-run |
Total 9.8s ·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).