b09e418 · 11,059 commits · 10,326 files
Issued 2026-11-03
Nothing significant. Questions worth asking about Security & Reliability Posture, Product & Engineering Maturity. People was not rated.
101 checks ran across 6 assessable dimensions. None found a significant problem; 4 raised something worth a question. 15 findings, each with evidence. One dimension cannot be assessed without an acquirer. Last commit 21 October 2026.
- 04.62 Releases are cut from another branch than the one surveyed
- 2 findings from checks Borehole's calibration found wrong more often than right are no longer published.
- 3 findings about one contributor are withheld: one author wrote nearly all of this repository's commits; a buyer of this report reads them.
- The file and line of 5 credential-shaped matches are 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 | adequate | |
| 03 | Organization & Key-Person Risk | not assessable | |
| 04 | Product & Engineering Maturity | adequate | |
| 05 | Security & Reliability Posture | adequate | |
| 06 | Observability & Operations | adequate | |
| 07 | Fit with the Acquirer | not assessable |
- 9% 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 ↑misc/install-bunkerweb.sh is 9,742 lines, 231× this codebase's median file
adequateThe median source file here is 42 lines. 22 files exceed 1,000 lines, the largest being 9,742. 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. Measured against its own codebase's median, it is larger than 93% of 382 surveyed projects' largest files.
A note that does not affect this rating: notes like it are common in well-run projects.
| line-count | misc/install-bunkerweb.sh:1 — 9,742 lines (231× median) |
| line-count | src/common/db/Database.py:1 — 6,691 lines (159× median) |
| line-count | src/ui/app/static/js/pages/template_edit.js:1 — 5,043 lines (120× median) |
| line-count | src/ui/app/static/js/plugins-settings.js:1 — 4,225 lines (100× median) |
| line-count | src/ui/app/static/js/pages/reports.js:1 — 2,184 lines (52× median) |
Respond to this finding
Your response is published beside the finding, not instead of it. A finding you can argue with is the point — and a wrong one is calibration data we want.
An owner's response is removed only when it is unlawful, impersonates someone, publishes personal data or a credential, or is not about the finding. Disagreeing with the report is never a reason. To report a response, or to reach us about one, write to takedown@borehole.dev.
Engineering Process & SDLC Maturity
02 · adequate · ratings ↑Tests cover a thin slice of the codebase
adequate406 test files against 4,529 source files (9.0%). 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 | 406 test files / 4,529 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.
6% of recent commits change more than 2,000 lines
adequate183 of 3254 commits in the last 24 months changed over 2,000 lines of code, not counting reformatting, renames, vendored or generated code. A change that size is rarely reviewed line by line. Ask how they were reviewed, and what made them that large.
| git log --numstat | 183 commits over 2,000 lines |
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 · not assessable · ratings ↑Not rated: one author wrote nearly all of this repository's commits, so a finding about one contributor would be about someone its history all but names; the public report does not carry those, and does not rate this dimension without them. What a person adds here.
Product & Engineering Maturity
04 · adequate · ratings ↑3% of bug fixes add or change a test
adequateOf 1345 fixes in the last 24 months, 42 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 | 42 of 1345 |
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.
Effort is shifting from building to rewriting
adequateDeleted lines per line added rose from 0.11 to 0.87 between the first and second halves of this history. Rework is normal and often healthy, but a rising ratio means an increasing share of the team's time is spent replacing code that already exists rather than building what does not. Whether that is deliberate repayment or churn is a question for the team.
A note that does not affect this rating: in Borehole's calibration, this check's notes were usually true but overstated.
| deletions-per-insertion | first half 0.11, second half 0.87 (split 2023-03-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.
Releases are cut from another branch than the one surveyed
adequateThe newest pre-release, v1.6.18-rc2, is not on the branch this survey read; the newest release on it is v1.6.17. The shipped product may differ from what this report describes. Survey the release branch too.
A note that does not affect this rating: notes like it are common in well-run projects.
| ee19d6d64 | tag v1.6.18-rc2 |
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 ↑4 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 | misc/migration/Dockerfile — runs as root |
| no-USER-instruction | src/deps/src/lua-resty-http/Dockerfile — runs as root |
| no-USER-instruction | src/deps/src/lua-resty-session/dev/Dockerfile — runs as root |
| no-USER-instruction | src/deps/src/modsecurity-nginx/win32/docker/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.
198 credential-shaped strings exist in the history
adequateMatches for private key block were committed at some point across 9,029 commits examined. Some of the files that held them are still in the working tree. What matters is whether each was rotated after it was committed. 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. 10 other matchs set aside: expired tokens, licence tokens a vendor verifies with a public key, or placeholder text where a key would go. None grants access to anything.
A note that does not affect this rating: notes like it are common in well-run projects.
| history | 5 cited: private key block pattern added here |
| 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.
The build runs third-party code it does not pin
adequate2 steps pipe a download straight into a shell. 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.
| misc/install-bunkerweb.sh | misc/install-bunkerweb.sh:843 — download piped into a shell |
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 of 8 Kubernetes workloads declare no resource limits
adequate8 workload manifests set no CPU or memory limits. One pod that leaks memory or spins can starve everything else on its node, and the scheduler cannot plan capacity for what it cannot see.
A note that does not affect this rating: in Borehole's calibration, this check's notes were usually true but overstated.
| misc/integrations/k8s.mariadb.ui.yml | misc/integrations/k8s.mariadb.ui.yml — workload with no limits |
| misc/integrations/k8s.mariadb.yml | misc/integrations/k8s.mariadb.yml — workload with no limits |
| misc/integrations/k8s.mysql.ui.yml | misc/integrations/k8s.mysql.ui.yml — workload with no limits |
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.
13 vendored components with no licence
adequateThird-party code is committed into this repository without any statement of the terms it arrived under. Unknown terms are harder to deal with than inconvenient ones: an awkward licence can be complied with, an absent one cannot. Each of these needs its origin established before the code changes hands.
A note that does not affect this rating: in Borehole's calibration, this check's notes were usually true but overstated.
| src/all-in-one/deps/crowdsec.json | src/all-in-one/deps/crowdsec.json — 1 tracked files, no licence file |
| src/all-in-one/deps/go.json | src/all-in-one/deps/go.json — 1 tracked files, no licence file |
| src/all-in-one/deps/re2.json | src/all-in-one/deps/re2.json — 1 tracked files, no licence file |
| src/deps/deps.json | src/deps/deps.json — 1 tracked files, no licence file |
| src/deps/init_deps.sh | src/deps/init_deps.sh — 1 tracked files, no licence file |
| src/deps/install.sh | src/deps/install.sh — 1 tracked files, no licence 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.
16 advisories against this project in the last 24 months, 5 high or critical
adequateThe newest was published on 2026-09-21. A project that publishes advisories is telling its users about its fixes, and the count and pace say how much security work it carries. None of them affects the surveyed version.
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.
| GHSA-xcv3-gjwr-rwxw | 2026-09-21: GHSA-xcv3-gjwr-rwxw (high), fixed in 1.1.0: Unauthenticated RCE via the BunkerWeb Worker API in the Official Kubernetes Sidecar Configuration |
| GHSA-vqvw-37gh-5w49 | 2026-09-21: GHSA-vqvw-37gh-5w49 (low), fixed in 1.6.15: Cross-Service Custom Configuration Move via Unauthorized Destination |
| GHSA-j2mq-vqhg-c5mr | 2026-09-21: GHSA-j2mq-vqhg-c5mr (moderate), fixed in 1.6.15: Cache Deletion Crosses the Job-Run Permission Boundary |
| GHSA-7w87-8gxh-2x99 | 2026-09-21: GHSA-7w87-8gxh-2x99 (low), fixed in 1.6.15: Service Conversion Permission Bypass in the Fine-Grained API ACL |
| GHSA-cvfx-2ffg-cqmj | 2026-09-21: GHSA-cvfx-2ffg-cqmj (high), fixed in 1.6.15: Bypass filename rules via `filename*=` parameter |
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 ↑No structured logging library is in use
adequateNothing references a structured logging library. Logs that are written to be read by a person are not searchable by a machine, which means incident response here is proportional to how well someone remembers the codebase rather than to what the tooling can find.
| logging-scan | C source is not searched: C programs log through printf-style calls unless they take a library, and none of the 10 searched for is referenced |
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.
2 of 10 deployed images carry no version, or `latest`
adequate2 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.
| misc/dev/ticket-3755-le-dns-env-stale/docker-compose.yml | misc/dev/ticket-3755-le-dns-env-stale/docker-compose.yml:95 — image without a version |
| misc/dev/ticket-3755-le-dns-env-stale/docker-compose.yml | misc/dev/ticket-3755-le-dns-env-stale/docker-compose.yml:111 — 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
9 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 The tree carries design documentation (docs/diagrams/concepts.drawio and 17 more). Does it match what the team believes today? Ask them to walk through it against the code.
- 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 coverageNot rated: one author wrote nearly all of this repository's commits, so a finding about one contributor would be about someone its history all but names; the public report does not carry those, and does not rate this dimension without them.
- Which of the people who wrote this are part of the transaction, and for how long after it?
- Who mentors whom, and would that survive a departure?
- Can the team grow, and who stands behind the top three contributors?
- Is the seniority mix sound, and will pay survive your salary bands?
- Is the pace sustainable? Commit times cannot say: git keeps no reliable local time.
- Does the team want to stay after close?
- How are decisions made and disagreements resolved?
Product & Engineering Maturity
04 · minimal coverage- Can this team deliver the stated roadmap on the stated timeline?
- Does leadership know about the debt, and is time budgeted to repay it?
- Is the engineering shape consistent with the commercial story?
Security & Reliability Posture
05 · partial coverage- measured 05.5 found credential-shaped strings in this repository. Was each one revoked at the provider? Deleting it from the code revokes nothing; only the provider's audit log shows that it was.
- measured No threat model is in the tree of what looks like a running service. Does one exist elsewhere, and who owns it?
- What has actually broken, how often, and how badly?
- What did external testing find, and was it fixed?
- What is the SOC 2, ISO 27001 or GDPR status, and where is the evidence?
Observability & Operations
06 · partial coverage- measured Backup or restore tooling is in the tree (src/common/core/backup/backup.py). Has a restore ever been rehearsed, and how long did it take?
- 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 C codebase, with Python alongside (15% of source files). Does your engineering organisation already run C in production, or would this be the first?
- The bulk of this system sits in src/, misc/. Which of your existing systems would each of those have to absorb or replace?
- The repository carries deployment configuration (misc/dev/docker-compose.all-in-one.api.yml and 41 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/bunkerity/bunkerweb/b09e418)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 — 86 signals that ran and did not fire
Appendix: rejection log — 86 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 — 62
| Signal | What it found |
|---|---|
| 04.hotspot_concentration | change is spread across the codebase rather than pooling in a few filesfiles 64,761 · top5 share 0.008 |
| 04.debt_markers | debt markers are sparsemarkers 729 · per kloc 0.36 · lines read 2,051,422 |
| 04.dependency_sprawl | direct dependency counts are unremarkable |
| 04.test_growth | test effort kept pace with code writtenlate test per code 0.067 · early test per code 0.023 |
| 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.schema_churn | columns, once added, staydropped within 90 days 0 · columns added last year 24 |
| 04.compat_layers | little code is kept for the old wayshare 0.002 · code files 4,180 · compat files 8 |
| 06.telemetry_presence | a telemetry or error-reporting library is referencednote presence only; whether anyone watches it is not visible here · matches 2 |
| 06.healthcheck_presence | a health or readiness check is defined |
| 06.usage_reporting_default | the product's code names no reporting hostsettings on 0 · settings off 0 |
| 06.probes_identical | readiness and liveness are distinct, or not both setidentical 0 · workloads with both 8 |
| 06.release_markers | releases are markedtags last year 50 · release commits 0 · changelog commits 682 |
| 06.migrate_on_start | migrations do not run at container start |
| 03.active_contributors | withheld: this check's result would describe one person |
| 03.knowledge_silos | withheld: this check's result would describe one person |
| 03.drive_by_contributors | withheld: this check's result would describe one person |
| 03.contributor_attrition | withheld: this check's result would describe one person |
| 03.bus_factor_trend | withheld: this check's result would describe one person |
| 03.joiners_and_leavers | withheld: this check's result would describe one person |
| 02.merge_discipline | a meaningful share of recent change carries evidence of reviewmerges 986 · window last 24 months · with tracked 3 |
| 02.ci_presence | CI configuration is present in the working treecount 47 |
| 02.release_cadence | tags are presenttags 116 |
| 02.conventional_commits | commit subjects generally carry contentsampled 9,119 · low content share 0.007 |
| 02.branch_protection_hints | process scaffolding is present in the repository |
| 02.ci_runs_tests | CI invokes a test runnerconfigs 47 · with tests 23 |
| 02.skipped_tests | few tests are switched offfocused 0 · skipped 1 · test files 1,154 |
| 02.ci_test_gating | no test run in CI is written so that it cannot failconfigs 47 |
| 02.revert_share | change is rarely undoneshare 0.008 · reverts 30 · recent commits 3,553 |
| 02.dependency_update_cadence | dependencies move with the codelockfiles 1 · commits since 50 · days since lockfile changed 6 |
| 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 6 · ci configs 47 · product files 4,180 |
| 02.long_lived_branches | the typical branch reaches the trunk quicklyshare 0.353 · merges 150 · long lived 53 |
| 01.initial_dump | first commit is not a disproportionate share of the codebaseinsertions 2 · share of insertions 0.0 |
| 01.message_uniformity | commit subjects vary in wording and lengthlength stdev 27.03 · repeat share 0.059 |
| 01.revision_depth | most files were revisited after they were first writtenfiles seen 7,640 · write once share 0.36 |
| 01.duplicated_blocks | little shipping code is repeated verbatim across filesshare 0.0224 · product files 688 · distinct blocks 96,874 |
| 01.build_reproducibility | every base image names a versionfloating 0 · from lines 16 |
| 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 paths; the only other matches are expired or licence tokens or placeholders, which grant nothingnote the working tree only; the history is 05.5 · patterns 8 · files read 7,151 |
| 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_management_pattern | no environment file is committed outside tests and examplesenv files 0 |
| 05.known_vulnerabilities | no locked dependency has a published advisory; not assessed for C and C++ package managers, Mavenadvisories 0 · dependencies 119 · high or critical 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_copyleft_inherited | every licence found in vendored code is permissive or weak-copyleftvendored paths 6,958 |
| 05.license_grant_unclear | the licence is recognisable as AGPL-3.0class network-copyleft · license AGPL-3.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 328 · added in two years 108 · removed within 60 days 3 |
| 04.ci_platforms_dropped | no platform was dropped from CI in the last two years |
| 04.repository_status | the README's first screen states no end, move or freezestatements 0 |
| 02.development_elsewhere | nothing says development happens elsewhereno pr statements 0 · mirror statements 0 · replayed commit share 0.0 |
| 05.licence_changes | the root licence has not changed in the history readlicence versions 1 · unreleased changes 0 |
| 05.paid_edition | no directory carries a separate paid-edition licencedirectories 0 |
| 04.releases_stopped | releases keep pace with developmentmedian gap days 4.0 · days since last tag 4 · commits last 90 days 607 |
| 03.single_maintainer | withheld: this check's result would describe one person |
| 05.project_advisories | no published advisory affects the surveyed versionaffecting 0 · exploited 0 · advisories 16 |
| 05.project_exploited | no affecting advisory is on CISA's Known Exploited listexploited 0 |
Could not conclude, or did not apply — 24
Not a clean result. Each says why it could not answer here.
| Signal | Why |
|---|---|
| 04.dependency_redundancy | no JavaScript manifest to read |
| 06.telemetry_depth | none at all is 06.1 |
| 06.print_logging | not assessed for C: its logger calls are not read |
| 06.correlation_ids | not assessed for C, the language the product is written in: this check's patterns read other languages only |
| 06.alert_rules | no alert rules in the repository; they may live in a console |
| 06.single_replica | no Kubernetes deployments |
| 06.environment_branching | not assessed for C, 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 |
| 01.swallowed_errors | not assessed for C, 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.outbound_timeouts | not assessed for C, the language the product is written in: this check's patterns read other languages only |
| 05.migration_reversibility | too few migrations to judge |
| 05.sql_from_strings | not assessed for C, the language the product is written in: this check's patterns read other languages only |
| 05.shell_from_strings | not assessed for C, the language the product is written in: this check's patterns read other languages only |
| 05.unsafe_deserialization | not assessed for C, the language the product is written in: this check's patterns read other languages only |
| 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_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 |
Anyone can check this report against the authoritative record — click the stamp, or enter W5DD-FBEX-23FW 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/W5DDFBEX23FW?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: 1060.1authenticated: False |
| 61.0s | cloned the repository to a temporary directory | depth: full |
| 103.7s | read the git history | commits: 11059tracked files: 10326 |
| 511.6s | ran the deterministic checks | blame pass: Falseread working tree: False |
| 511.7s | recorded where this scan ran | attested: Falseenvironment: cloud-run |
| 856.9s | kept the facts, never the source, for re-reading under new checks | |
| 856.9s | deleting the working copy |
Total 856.9s ·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).