c49fff6 · 1,422 commits · 140 files
Issued 2026-10-22
FSL-1.1-ALv2 since 2024-02-27: source available, not open source; a competing commercial product or service is not allowed; each version becomes Apache-2.0 two years after its release.
106 checks ran across 6 assessable dimensions. None found a significant problem; 6 raised something worth a question. 15 findings, each with evidence. One dimension cannot be assessed without an acquirer.
- 05.60 FSL-1.1-ALv2 since 2024-02-27: source available, not open source; a competing commercial product or service is not allowed; each version becomes Apache-2.0 two years after its release
- 05.66 The licence is FSL-1.1-ALv2: source available, not open source LICENSE.md:1
- 05.60 Relicensed: BUSL-1.1 → FSL-1.0-ALv2 (2023-11-17) → FSL-1.1-ALv2 (2024-02-27) LICENSE
- states a policy on AI-generated contributions CONTRIBUTING.md:87
| Dimension | Rating | ||
|---|---|---|---|
| 01 | Architecture & Codebase — including AI provenance | adequate | |
| 02 | Engineering Process & SDLC Maturity | adequate | |
| 03 | Organization & Key-Person Risk | adequate | |
| 04 | Product & Engineering Maturity | adequate | |
| 05 | Security & Reliability Posture | adequate | |
| 06 | Observability & Operations | adequate | |
| 07 | Fit with the Acquirer | not assessable |
- 14% 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 138 of 138 counted files
Architecture & Codebase — including AI provenance
01 · adequate · ratings ↑2 base images float: no version, or `latest`
adequate2 of 5 `FROM` lines in product Dockerfiles name an image without a version, or with `latest`. Each build pulls whatever the registry serves that day, so the image that ships can change without a commit, and last month's build cannot be reproduced. Pin a version, or a digest.
| workstation/postinstall/Dockerfile | workstation/postinstall/Dockerfile:2 — base image without a version |
| workstation/preinstall/Dockerfile | workstation/preinstall/Dockerfile:2 — base image without a version |
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 · adequate · ratings ↑Tests cover a thin slice of the codebase
adequate4 test files against 64 source files (6.2%). This does not measure whether the tests are good, only whether enough of them exist for the codebase to be changed safely by someone who did not write it — which is exactly the situation after an acquisition.
| test-file-ratio | 4 test files / 64 source 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 ↑The contributor who wrote a quarter or more of this has not committed here for more than six months
adequateOne person authored a quarter or more of 1,005 commits and has not committed here for more than six months, 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 six months ago, measured to the survey |
| git shortlog -sn | top author a quarter or more of 1,005 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 · adequate · ratings ↑10% of bug fixes add or change a test
adequateOf 79 fixes in the last 24 months, 8 touched a test. A fix without the test that would have caught the bug can quietly come back, and the suite never learns from what went wrong.
| fix commits touching tests | 8 of 79 |
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.
Change keeps returning to the same few files
adequateFive files out of 223 absorb 34% 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.
A note that does not affect this rating: in Borehole's calibration, this check's notes were usually true but overstated.
| touch-count | docker-compose.yml — 245 commits touched it |
| touch-count | install.sh — 114 commits touched it |
| touch-count | sentry/sentry.conf.example.py — 100 commits touched it |
| touch-count | README.md — 95 commits touched it |
| touch-count | .github/workflows/test.yml — 91 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 · adequate · ratings ↑3 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 | clickhouse/Dockerfile — runs as root |
| no-USER-instruction | workstation/postinstall/Dockerfile — runs as root |
| no-USER-instruction | workstation/preinstall/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.
2 environment files are committed
adequate.env, optional-modifications/patches/external-kafka/.env.patch are 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 |
| optional-modifications/patches/external-kafka/.env.patch | optional-modifications/patches/external-kafka/.env.patch — 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.
The build runs third-party code it does not pin
adequate4 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/enforce-license-compliance.yml | .github/workflows/enforce-license-compliance.yml:22 — action pinned by tag |
| .github/workflows/lock.yml | .github/workflows/lock.yml:11 — 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.
2 outbound calls can wait forever
adequate2 HTTP calls use a client with no timeout (Python `requests` without `timeout=`, or Go's default client). When a dependency slows down, each one holds a worker until the connection gives up, and enough of them take the service down with the dependency.
A note that does not affect this rating: in Borehole's calibration, this check's notes were usually true but overstated.
| _integration-test/custom-ca-roots/custom-ca-roots-test.py | _integration-test/custom-ca-roots/custom-ca-roots-test.py:8 — outbound call without a timeout |
| _integration-test/custom-ca-roots/custom-ca-roots-test.py | _integration-test/custom-ca-roots/custom-ca-roots-test.py:12 — outbound call without a timeout |
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.
3 locked dependencies have published vulnerabilities, 4 high or critical
adequate3 of 46 locked dependencies match 7 published advisories in OSV, 4 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. None of the high or critical ones is in what the product ships: they are development dependencies.
A note that does not affect this rating: in Borehole's calibration, this check's notes were usually true but overstated.
| uv.lock | uv.lock — cryptography 48.0.1: GHSA-g6cj-pr64-35w5 (high), fixed in 50.0.0; a development dependency |
| uv.lock | uv.lock — urllib3 2.7.0: GHSA-8988-9cw3-xx77 (high), fixed in 2.8.0; a development dependency |
| uv.lock | uv.lock — idna 3.11: GHSA-65pc-fj4g-8rjx (moderate), fixed in 3.15; a development dependency |
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 FSL-1.1-ALv2: source available, not open source
adequateLICENSE.md grants FSL-1.1-ALv2: source available, not open source; a competing commercial product or service is not allowed; each version becomes Apache-2.0 two years after its release. 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.md | LICENSE.md:1 — 105 lines, FSL-1.1-ALv2 |
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: BUSL-1.1 → FSL-1.0-ALv2 (2023-11-17) → FSL-1.1-ALv2 (2024-02-27)
adequateThe root licence changed 2 time(s). Code taken under earlier terms stays under them; check which terms any fork or customer relied on.
A note that does not affect this rating: a licence change is a fact for the first screen, and only a narrowing of rights within two years of the surveyed commit costs "strong".
| bd6817e8f | LICENSE — BUSL-1.1 from 2020-12-15 |
| bd1d1d822 | LICENSE — FSL-1.0-ALv2 from 2023-11-17 |
| d5e2f8270 | LICENSE.md — FSL-1.1-ALv2 from 2024-02-27 |
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 advisory against this project in the last 24 months, 1 high or critical
adequateThe newest was published on 2025-01-15. A project that publishes advisories is telling its users about its fixes, and the count and pace say how much security work it carries. Whether 1 of them are fixed in the code you ship could not be told from this history: its version is only known to be at least 26.10.0. Answer lives in: the release you run, set against each fixed version. The record is incomplete: NVD: 33 records name self-hosted with nothing tying them to this repository (CVE-2025-0337, CVE-2025-11449, CVE-2025-11450, …).
A note that does not affect this rating: it describes the project's advisory record, and no advisory in it is known to affect the surveyed commit.
| CVE-2025-22146 | 2025-01-15: CVE-2025-22146 (critical): Sentry is a developer-first error tracking and performance monitoring tool. A critical vulnerability was discovered in the SAML SSO implementation of Sentry. 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.
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.
1 of 18 deployed images carry no version, or `latest`
adequate1 images in the deployment configuration are named without a version or as `latest`. A redeploy can change the software without a commit, a rollback has nothing to roll back to, and nobody can say from the repository what is running.
A note that does not affect this rating: in Borehole's calibration, this check's notes were usually true but overstated.
| docker-compose.yml | docker-compose.yml:127 — image without a version |
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
6 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 198 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 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 Python codebase, with JavaScript alongside (40% of source files). Does your engineering organisation already run Python in production, or would this be the first?
- The bulk of this system sits in _integration-test/, install/, sentry/. Which of your existing systems would each of those have to absorb or replace?
- The repository carries deployment configuration (clickhouse/Dockerfile and 6 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/getsentry/self-hosted/c49fff6)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 — 91 signals that ran and did not fire
Appendix: rejection log — 91 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 — 60
| Signal | What it found |
|---|---|
| 04.debt_markers | debt markers are sparsemarkers 8 · per kloc 0.88 · lines read 9,112 |
| 04.dependency_sprawl | direct dependency counts are unremarkable |
| 04.test_growth | test effort kept pace with code writtenlate test per code 0.146 · early test per code 0.0 |
| 04.churn_trend | rework is not rising against new worklate delete per insert 0.504 · early delete per insert 0.589 |
| 04.eol_runtime | every pinned runtime is still supportedeol as of 2026-09-24 |
| 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 60 · 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 17 |
| 06.healthcheck_presence | a health or readiness check is defined |
| 06.telemetry_depth | the service is visible in more than one way |
| 06.error_reporting | an error reporter is initialisedinitialised 1 · config files 0 |
| 06.usage_reporting_default | the product's code names no reporting hostsettings on 0 · settings off 0 |
| 06.release_markers | releases are markedtags last year 22 · release commits 16 · changelog commits 26 |
| 06.migrate_on_start | migrations do not run at container start |
| 03.contributor_concentration | no single contributor dominates the last 24 monthsyears 10.7 · window last 24 months · authors 198 |
| 03.active_contributors | more than one contributor active in the trailing yearall time 198 · active 12mo 43 |
| 03.knowledge_silos | every substantial directory has been touched by more than one personauthors 198 · directories 4 |
| 03.drive_by_contributors | an open contributor base, where one-commit contributors are normalauthors 198 · one off share 0.722 |
| 03.critical_path_ownership | more than one person changes the critical pathsauthors 70 |
| 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 1 · joined 4 · regular last year 8 |
| 02.merge_discipline | a meaningful share of recent change carries evidence of reviewmerges 39 · window last 24 months · with tracked 13 |
| 02.ci_presence | CI configuration is present in the working treecount 7 |
| 02.release_cadence | tags are presenttags 121 |
| 02.conventional_commits | commit subjects generally carry contentsampled 1,305 · 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 7 · with tests 1 |
| 02.ci_test_gating | no test run in CI is written so that it cannot failconfigs 7 |
| 02.revert_share | change is rarely undoneshare 0.02 · reverts 6 · recent commits 297 |
| 02.dependency_update_cadence | dependencies move with the codelockfiles 2 · commits since 1 · days since lockfile changed 0 |
| 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 3 · ci configs 7 · product files 60 |
| 02.commit_size | changes arrive in reviewable sizesshare 0.0 · commits 236 · over 2000 lines 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 1 · share of insertions 0.0 |
| 01.message_uniformity | commit subjects vary in wording and lengthlength stdev 18.78 · repeat share 0.083 |
| 01.revision_depth | most files were revisited after they were first writtenfiles seen 102 · write once share 0.284 |
| 01.oversized_modules | no module is an outlier against this codebase's own normlargest 729 · threshold 1,000 · median lines 34 |
| 01.duplicated_blocks | little shipping code is repeated verbatim across filesshare 0.0074 · product files 60 · distinct blocks 1,900 |
| 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 120 |
| 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.secrets_in_history | no credential-shaped string was ever added outside test and fixture pathspatterns 8 · truncated False · added lines 20,896 |
| 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.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 8 · added in two years 3 · 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 11.5 · days since last tag 7 · commits last 90 days 86 |
| 04.release_branch | the newest release was cut from the branch surveyedelsewhere 11 · on branch 108 · tags in window 119 |
| 03.single_maintainer | no file says one person maintains itstatements 0 |
Could not conclude, or did not apply — 31
Not a clean result. Each says why it could not answer here.
| Signal | Why |
|---|---|
| 04.schema_churn | no schema migrations to read |
| 04.dependency_redundancy | no JavaScript manifest to read |
| 06.structured_logging | not assessed for Shell: its logging setup is not read |
| 06.print_logging | not assessed for Shell: its logger calls are not read |
| 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.environment_branching | not assessed for Shell, the language the product is written in: this check's patterns read other languages only |
| 06.feature_flags | no feature-flag service; flags may live elsewhere |
| 02.skipped_tests | too few test files to judge how many are switched off |
| 02.long_lived_branches | too few merges to judge (squash and rebase leave none) |
| 01.swallowed_errors | not assessed for Shell, the language the product is written in: this check's patterns read other languages only |
| 01.notebook_outputs | not a data or machine-learning repository |
| 05.migration_reversibility | too few migrations to judge |
| 05.sql_from_strings | not assessed for Shell, the language the product is written in: this check's patterns read other languages only |
| 05.shell_from_strings | not assessed for Shell, the language the product is written in: this check's patterns read other languages only |
| 05.unsafe_deserialization | not assessed for Shell, the language the product is written in: this check's patterns read other languages only |
| 05.tls_verification_off | not assessed for Shell, the language the product is written in: this check's patterns read other languages only |
| 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 |
| 05.project_advisories | record incomplete: no advisory found in the sources that answered; NVD: 33 records name self-hosted with nothing tying them to this repository (CVE-2025-0337, CVE-2025-11449, CVE-2025-11450, …) |
| 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 3CH7-XBWC-08G4 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/3CH7XBWC08G4?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: 2.5authenticated: False |
| 1.4s | cloned the repository to a temporary directory | depth: full |
| 1.8s | read the git history | commits: 1422tracked files: 140 |
| 17.7s | ran the deterministic checks | blame pass: Trueread working tree: False |
| 17.7s | recorded where this scan ran | attested: Falseenvironment: cloud-run |
| 19.6s | kept the facts, never the source, for re-reading under new checks | |
| 19.6s | deleting the working copy |
Total 19.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).