3456769 · 6,569 commits · 2,771 files
Issued 2026-10-23
BUSL-1.1 since 2026-09-22: source available, not open source; production use restricted until the change date.
102 checks ran across 6 assessable dimensions. 1 finding is worth checking first. 14 findings, each with evidence. One dimension cannot be assessed without an acquirer.
- 05.60 BUSL-1.1 since 2026-09-22: source available, not open source; production use restricted until the change date
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 18 locked dependencies have published vulnerabilities, 20 high or critical in what ships
- 4 findings from checks Borehole's calibration found wrong more often than right are no longer published.
- The file and line of 1 credential-shaped match is withheld. File and line are shown to whoever GitHub says controls this repository, signed in, and to a buyer of this report.
| 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 | adequate | |
| 07 | Fit with the Acquirer | not assessable |
- 18% 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
Architecture & Codebase — including AI provenance
01 · strong · ratings ↑pkg/api/controller.go is 6,106 lines, 71× this codebase's median file
adequateThe median source file here is 86 lines. 8 files exceed 1,000 lines, the largest being 6,106. 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 | pkg/api/controller.go:1 — 6,106 lines (71× median) |
| line-count | pkg/graveler/graveler.go:1 — 4,015 lines (46× median) |
| line-count | pkg/catalog/catalog.go:1 — 3,571 lines (41× median) |
| line-count | webui/src/pages/repositories/repository/objects.jsx:1 — 1,609 lines (18× median) |
| line-count | webui/src/lib/api/index.js:1 — 1,500 lines (17× 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.
A move from JavaScript to TypeScript began 48 months ago and is 39% done
adequate38 product files are in the new language and 59 are still in the old one, 48 months after the first new file appeared. The new language's share of the lines rose from 0% to 20%, and moved 3 percentage points in the last year. Two languages for one job doubles what an engineer has to know, and the unmoved half is usually what nobody wants to touch. Ask whether finishing it is planned, and what it costs.
A note that does not affect this rating: in Borehole's calibration, this check's notes were usually true but overstated.
| file counts | 59 old, 38 new |
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 ↑93 direct dependencies in a single manifest
adequatego.mod declares 93 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 — 93 declared |
| direct-dependencies | webui/package.json — 39 declared |
| direct-dependencies | clients/python/pyproject.toml — 4 declared |
| direct-dependencies | clients/python-wrapper/pyproject.toml — 2 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.
15 files still carry code deprecated more than two years ago
adequate15 files were marked deprecated over two years ago and still are, the oldest since Apr 2021. A deprecation is a promise to remove. Ask what still depends on these, and whether removing them is scheduled.
A note that does not affect this rating: in Borehole's calibration, this check's notes were usually true but overstated.
| pkg/catalog/catalog.pb.go | pkg/catalog/catalog.pb.go — deprecated since Apr 2021 |
| pkg/block/adapter.go | pkg/block/adapter.go — deprecated since Apr 2021 |
| pkg/catalog/model.go | pkg/catalog/model.go — deprecated since Apr 2021 |
| pkg/graveler/graveler.pb.go | pkg/graveler/graveler.pb.go — deprecated since Jun 2021 |
| pkg/graveler/settings/test_settings.pb.go | pkg/graveler/settings/test_settings.pb.go — deprecated since Sep 2021 |
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 ↑1 credential-shaped string committed to the tree
adequateMatches for AWS access key appear in tracked files outside test and fixture paths. They stay in the history even after they leave the tree, so what matters is whether each was rotated. The code cannot tell whether any of them is live, and that decides whether this matters: none sits in production configuration, and none is in a format its provider keeps for live keys. Is any of these live? Show that each was rotated after it was committed, and when.
| AWS access key | AWS access key pattern matched |
| File and line are shown to whoever GitHub says controls this repository, signed in, and to a buyer of this report. |
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.
18 locked dependencies have published vulnerabilities, 20 high or critical in what ships
adequate worth checking first18 of 964 locked dependencies match 58 published advisories in OSV, 30 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 and the 1 other file it cites settles it. If it holds when someone checks it, this finding is significant.
| go.mod | go.mod — github.com/getkin/kin-openapi v0.131.0: GHSA-r277-6w6q-xmqw (critical), fixed in 0.144.0 |
| webui/package-lock.json | webui/package-lock.json — dompurify 3.4.12: GHSA-cg2g-xh64-v4q7 (critical), fixed in 3.4.17 |
| go.mod | go.mod — github.com/labstack/echo/v4 v4.11.4: GHSA-cxf3-9h37-7rr8 (critical), fixed in 4.16.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.
The production build publishes source maps
adequateThe build configuration emits source maps for production, so the original source, with its comments and structure, is downloadable by every visitor. Upload them to an error tracker and keep them off the public server instead.
| webui/vite.config.mts | webui/vite.config.mts:66 — source maps in a production build |
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.
Relicensed: Apache-2.0 → BUSL-1.1 (2026-09-22)
adequateThe root licence changed 1 time(s). The latest terms restrict what users, hosts or a buyer may do in ways the earlier ones did not. Code taken under the old terms stays under them, so both matter in diligence.
| 3cbd4bc3c | LICENSE — Apache-2.0 from 2020-08-02 |
| 358544dd7 | LICENSE — BUSL-1.1 from 2026-09-22 |
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.
10 advisories against this project in the last 24 months, 3 high or critical
adequateThe newest was published on 2026-10-01. A project that publishes advisories is telling its users about its fixes, and the count and pace say how much security work it carries.
| GHSA-96f7-c79c-crg8 | 2026-10-01: GHSA-96f7-c79c-crg8 (high), fixed in 1.103.0: S3 gateway accepts unsigned headers on presigned URLs, allowing reads with the signer's permissions |
| GHSA-223c-qwgx-wwcg | 2026-10-01: GHSA-223c-qwgx-wwcg (moderate): Server-side request forgery (SSRF) via action hooks (webhook, Airflow, Lua net/http) |
| GHSA-gf2q-q6wc-x7fm | 2026-08-05: GHSA-gf2q-q6wc-x7fm (low): Improper access control: user can list branches via S3 gateway ListObjects API without the fs:ListBranches permission |
| CVE-2026-66006 | 2026-07-24: CVE-2026-66006 (moderate): lakeFS through 1.83.0, fixed in commit 71a45ee, contains an authentication bypass vulnerability in the /setup_comm_prefs endpoint that allows unauthenticated at |
| GHSA-c2r5-5j4w-2xff | 2026-05-21: GHSA-c2r5-5j4w-2xff (high), fixed in 1.81.1: stored XSS in rendered markdown previews via raw HTML |
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 build runs third-party code it does not pin
adequate20 third-party CI actions are referenced by a tag or branch rather than a commit, so they run whatever that tag points to on the day. Tags have been moved to malicious commits in real supply-chain attacks, and a piped script is whatever the server returns that minute. Pinning to a commit is the fix, and it is small.
A note that does not affect this rating: notes like it are common in well-run projects.
| .github/workflows/check-webui-docs-links.yaml | .github/workflows/check-webui-docs-links.yaml:37 — action pinned by tag |
| .github/workflows/claude.yml | .github/workflows/claude.yml:35 — action pinned by tag |
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 deserialiser that can run code
adequate1 places read data with a deserialiser that executes what it reads (`yaml.load` without a safe loader). That is safe on data the system wrote itself and remote code execution on anything else. Ask where each one's input comes from.
A note that does not affect this rating: in Borehole's calibration, this check's notes were usually true but overstated.
| clients/python-wrapper/lakefs/config.py | clients/python-wrapper/lakefs/config.py:131 — code-executing deserialiser |
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 licence is BUSL-1.1: source available, not open source
adequateLICENSE grants BUSL-1.1: source available, not open source; production use restricted until the change date. The reading comes from the licence's own title and clauses. Whether the terms fit the buyer's intended use, and whether any paid licence transfers with the code, is a question for counsel and the licensor.
A note that does not affect this rating: it names the project's licence, a fact for the first screen rather than a weakness.
| LICENSE | LICENSE:1 — 150 lines, BUSL-1.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.
Observability & Operations
06 · adequate · ratings ↑Sends usage data to stats.lakefs.io by default
adequatepkg/config/defaults.go sends to stats.lakefs.io, and clients/python/lakefs_sdk/api/internal_api.py leaves reporting on as shipped. Every installation reports to the vendor unless its operator turns this off. For a buyer running it inside their own product, that is an outbound data flow to a third party: ask what is sent, how often, and whether the buyer's customers were told.
| pkg/config/defaults.go | pkg/config/defaults.go:115 — reports to stats.lakefs.io |
| clients/python/lakefs_sdk/api/internal_api.py | clients/python/lakefs_sdk/api/internal_api.py:1527 — the reporting setting is on by default |
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.
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
7 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 1,513 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 120 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.1 and 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, with Java alongside (16% of source files). Does your engineering organisation already run Go in production, or would this be the first?
- The bulk of this system sits in clients/, pkg/, webui/. Which of your existing systems would each of those have to absorb or replace?
- The repository carries deployment configuration (Dockerfile and 5 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/treeverse/lakefs/3456769)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 — 88 signals that ran and did not fire
Appendix: rejection log — 88 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 — 69
| Signal | What it found |
|---|---|
| 04.hotspot_concentration | change is spread across the codebase rather than pooling in a few filesfiles 10,233 · top5 share 0.031 |
| 04.debt_markers | debt markers are sparsemarkers 885 · per kloc 2.12 · lines read 417,960 |
| 04.test_growth | test effort kept pace with code writtenlate test per code 0.293 · early test per code 0.207 |
| 04.churn_trend | rework is not rising against new worklate delete per insert 0.722 · early delete per insert 0.617 |
| 04.fixes_with_tests | fixes usually come with a testfixes 207 · share 0.266 · with tests 55 |
| 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 1,131 · compat files 0 |
| 04.dependency_redundancy | one library per job, mostly |
| 06.telemetry_presence | a telemetry or error-reporting library is referencednote presence only; whether anyone watches it is not visible here · matches 4 |
| 06.structured_logging | a structured logging library is referencedmatches 6 |
| 06.healthcheck_presence | a health or readiness check is defined |
| 06.telemetry_depth | the service is visible in more than one way |
| 06.correlation_ids | a request can be followed through the logstracing False · request id sites 16 |
| 06.deployed_image_floats | every deployed image names a versionimages 4 · floating 0 |
| 06.environment_branching | environment differences live in configurationsites 0 |
| 06.release_markers | releases are markedtags last year 29 · release commits 9 · changelog commits 52 |
| 06.migrate_on_start | migrations do not run at container start |
| 03.contributor_concentration | no single contributor dominates the last 24 monthsyears 7.1 · window last 24 months · authors 120 |
| 03.active_contributors | more than one contributor active in the trailing yearall time 120 · active 12mo 33 |
| 03.knowledge_silos | every substantial directory has been touched by more than one personauthors 120 · directories 11 |
| 03.drive_by_contributors | an open contributor base, where one-commit contributors are normalauthors 120 · one off share 0.45 |
| 03.contributor_attrition | no contributor dominates enough for their absence to matterauthors 120 · 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 50 |
| 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 5 · joined 4 · regular last year 17 |
| 02.merge_discipline | a meaningful share of recent change carries evidence of reviewmerges 0 · window last 24 months · with tracked 27 |
| 02.ci_presence | CI configuration is present in the working treecount 30 |
| 02.test_presence | tests are present in a normal proportion to sourcetests 615 · source 1,732 · test ratio 0.355 |
| 02.release_cadence | tags are presenttags 324 |
| 02.conventional_commits | commit subjects generally carry contentsampled 6,203 · low content share 0.009 |
| 02.branch_protection_hints | process scaffolding is present in the repository |
| 02.ci_runs_tests | CI invokes a test runnerconfigs 30 · with tests 6 |
| 02.skipped_tests | few tests are switched offfocused 0 · skipped 17 · test files 745 |
| 02.ci_test_gating | no test run in CI is written so that it cannot failconfigs 30 |
| 02.revert_share | change is rarely undoneshare 0.001 · reverts 1 · recent commits 1,146 |
| 02.dependency_update_cadence | dependencies move with the codelockfiles 5 · commits since 12 · days since lockfile changed 52 |
| 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 9 · ci configs 30 · product files 1,131 |
| 02.commit_size | changes arrive in reviewable sizesshare 0.019 · commits 1,018 · over 2000 lines 19 |
| 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 3 · share of insertions 0.0 |
| 01.message_uniformity | commit subjects vary in wording and lengthlength stdev 18.29 · repeat share 0.048 |
| 01.revision_depth | most files were revisited after they were first writtenfiles seen 1,351 · write once share 0.293 |
| 01.duplicated_blocks | little shipping code is repeated verbatim across filesshare 0.0032 · product files 698 · distinct blocks 76,669 |
| 01.swallowed_errors | errors are rarely thrown awayloc 420,320 · files 6 · per kloc 0.02 |
| 01.build_reproducibility | every base image names a versionfloating 0 · from lines 7 |
| 01.weights_in_git | no model weights are committedfiles 0 |
| 05.security_guardrails | at least one standard guard rail is configured |
| 05.dependency_pinning | a lockfile is committed, so builds are reproduciblelockfile True |
| 05.license_present | a licence file is presentfound True |
| 05.container_runs_as_root | every shipped Dockerfile drops to a non-root user or builds on a non-root base imagedockerfiles 2 |
| 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 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.privileged_workloads | no workload runs privileged or in the host's namespacessites 0 · behind a setting or built here 0 |
| 05.signing_material | no signing keystore or profile is committedfiles 0 |
| 05.cleartext_traffic | plain HTTP is not allowed app-widesites 0 |
| 05.license_vendored_unlicensed | no vendored third-party code is committedcomponents 0 |
| 05.committed_native_libraries | no widely used compiled library is committed to the productlibraries 0 |
| 04.dependency_churn | few dependencies were added and dropped within 60 daysdependencies seen 378 · added in two years 141 · removed within 60 days 0 |
| 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.paid_edition | no directory carries a separate paid-edition licencedirectories 0 |
| 04.releases_stopped | releases keep pace with developmentmedian gap days 13.0 · days since last tag 22 · commits last 90 days 21 |
| 04.release_branch | the newest release was cut from the branch surveyedelsewhere 3 · on branch 267 · tags in window 270 |
| 03.single_maintainer | no file says one person maintains itstatements 0 |
Could not conclude, or did not apply — 19
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 |
| 06.print_logging | a frontend: console output is the browser's, not the server's |
| 06.alert_rules | no alert rules in the repository; they may live in a console |
| 06.probes_identical | no Kubernetes probes |
| 06.single_replica | no Kubernetes deployments |
| 06.feature_flags | no feature-flag service; flags may live elsewhere |
| 02.long_lived_branches | too few merges to judge (squash and rebase leave none) |
| 01.notebook_outputs | not a data or machine-learning repository |
| 05.migration_reversibility | too few migrations to judge |
| 05.resource_limits | no Kubernetes workload manifests |
| 05.public_env_secret | not assessed for Go, the language the product is written in: this check's patterns read other languages only |
| 05.unsafe_html | not assessed for Go, the language the product is written in: this check's patterns read other languages only |
| 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 |
| 05.project_exploited | no affecting advisory is on CISA's Known Exploited list |
Anyone can check this report against the authoritative record — click the stamp, or enter 8C88-R60W-TDX8 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/8C88R60WTDX8?via=badge)
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 — 7 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 | read repository metadata from the GitHub API | size mb: 173.5authenticated: False |
| 16.7s | cloned the repository to a temporary directory | depth: full |
| 27.4s | read the git history | commits: 6569tracked files: 2771 |
| 197.6s | ran the deterministic checks | blame pass: Falseread working tree: False |
| 197.7s | recorded where this scan ran | attested: Falseenvironment: cloud-run |
| 282.4s | kept the facts, never the source, for re-reading under new checks | |
| 282.4s | deleting the working copy |
Total 282.4s ·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).