11d6b90 · 1,820 commits · 1,230 files
Issued 2026-11-03
Nothing proven significant. 1 finding is worth checking first. People was not rated.
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. Last commit 1 November 2026.
Borehole's proprietary scoring is calibrated across hundreds of repositories. Each finding here may be significant, and 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.
- 02.5 75% of commit subjects say nothing about the change
- 2 findings from checks Borehole's calibration found wrong more often than right are no longer published.
- 2 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 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 | adequate | |
| 03 | Organization & Key-Person Risk | not assessable | |
| 04 | Product & Engineering Maturity | strong | |
| 05 | Security & Reliability Posture | strong | |
| 06 | Observability & Operations | adequate | |
| 07 | Fit with the Acquirer | not assessable |
- 43% 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 1,208 of 1,208 counted files
Architecture & Codebase — including AI provenance
01 · strong · ratings ↑Commit messages are templated rather than written
adequate75% of commit subjects are exact repeats of another subject, and subject length varies by only 20.4 characters. A log written by someone explaining their reasoning to a future reader does not look like this. The log is therefore weak evidence of intent, whatever the code is like.
A note that does not affect this rating: in Borehole's calibration, this check's notes were usually true but overstated.
| commit-subjects | 32× 'v4.0.0.0' |
| commit-subjects | 29× 'v7.0.0.0' |
| commit-subjects | 27× 'Update README.md' |
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.
app/static/js/codemirror/lib/codemirror.js is 9,868 lines, 79× this codebase's median file
adequateThe median source file here is 124 lines. 6 files exceed 1,240 lines, the largest being 9,868. 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 | app/static/js/codemirror/lib/codemirror.js:1 — 9,868 lines (79× median) |
| line-count | app/modules/change/service.py:1 — 2,187 lines (17× median) |
| line-count | app/views/service/haproxy_section_views.py:1 — 1,557 lines (12× median) |
| line-count | app/modules/db/db_model.py:1 — 1,534 lines (12× median) |
| line-count | app/static/js/script.js:1 — 1,413 lines (11× 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.
96 errors caught and discarded in product code
adequate96 places catch an error and do nothing with it, across 37 files (0.5 per thousand lines). Each is a failure the system will not report. They surface later as problems nobody can explain, and they are cheap to fix now.
A note that does not affect this rating: in Borehole's calibration, this check's notes were usually true but overstated.
| app/jobs.py | app/jobs.py:82 — error caught and discarded |
| app/login.py | app/login.py:96 — error caught and discarded |
| app/modules/change/automation.py | app/modules/change/automation.py:675 — error caught and discarded |
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 ↑75% of commit subjects say nothing about the change
adequate worth checking first1,310 of 1,749 subjects are either under twelve characters or one of the standard placeholders — wip, fix, update. The history is therefore not usable for reconstructing why a decision was taken, which is the main thing an inheriting engineer needs it for. It says nothing about code quality and a great deal about how much context transfers with the asset.
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. If it holds when someone checks it, this finding is significant.
| commit-subject-content | 1,310/1,749 low-content subjects (74.9%) |
| example | 'Create 1' |
| example | 'Create 1' |
| example | 'Delete 1' |
| example | 'Create 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.
14% of recent commits change more than 2,000 lines
adequate24 of 170 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 | 24 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 · strong · ratings ↑No finding. 19 checks ran and none fired; the rejection log below says why each did not.
Security & Reliability Posture
05 · strong · ratings ↑31 dependencies float, and no lockfile is committed
adequateDependency versions are declared as ranges and no lockfile is committed, so a build today does not necessarily produce what a build last month produced. That matters twice over in a transaction: the thing being bought cannot be reproduced exactly, and a compromised upstream release arrives without anyone choosing to take it.
A note that does not affect this rating: in Borehole's calibration, this check's notes were usually true but overstated.
| unpinned | requirements.txt:1 — >=3.5.0 |
| unpinned | requirements.txt:2 — >=0.7,<1 |
| unpinned | requirements.txt:3 — >=1.35,<2 |
| unpinned | requirements.txt:4 — >=42 |
| unpinned | requirements.txt:5 — >=2.6,<3 |
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 credential-shaped string exists in the history
adequateMatches for private key block were committed at some point across 1,731 commits examined. The files that held them are no longer in the working tree — but removal from a file is not removal from the history, and the history is what transfers with the asset. 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.
A note that does not affect this rating: notes like it are common in well-run projects.
| history | 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.
4 of 4 Kubernetes workloads declare no resource limits
adequate4 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.
| helm/roxy-wi/templates/deployment-operations.yaml | helm/roxy-wi/templates/deployment-operations.yaml — workload with no limits |
| helm/roxy-wi/templates/deployment-scheduler.yaml | helm/roxy-wi/templates/deployment-scheduler.yaml — workload with no limits |
| helm/roxy-wi/templates/deployment-service-events.yaml | helm/roxy-wi/templates/deployment-service-events.yaml — 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.
Relicensed: LGPL-3.0 → Apache-2.0 (2018-07-17)
adequateThe root licence changed 1 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".
| 22db60f71 | LICENSE — LGPL-3.0 from 2018-01-15 |
| 38947903a | LICENSE — Apache-2.0 from 2018-07-17 |
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.
27 advisories against this project in the last 24 months, 22 high or critical
adequateThe newest was published on 2026-08-29. 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 9.2.0. Answer lives in: the release you run, set against each fixed 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-hp23-3cx2-4h2r | 2026-08-29: GHSA-hp23-3cx2-4h2r (high): Authenticated Path Traversal in /add/map Endpoint Allows Arbitrary File Read and Write |
| GHSA-9xc3-25r9-425m | 2026-08-29: GHSA-9xc3-25r9-425m (high): Authenticated SSRF and webhook hijack via Mattermost channel URL — role-3 user can force outbound to internal services |
| GHSA-3886-rcwf-vqjh | 2026-08-29: GHSA-3886-rcwf-vqjh (critical): Authenticated low-priv user can grant themselves superAdmin via POST /user/groups/save |
| GHSA-5hgx-fmqx-rcg8 | 2026-08-29: GHSA-5hgx-fmqx-rcg8 (critical): Authenticated low-priv user can change ANY user's password (account takeover) |
| GHSA-3wqc-vcrv-gfgr | 2026-08-29: GHSA-3wqc-vcrv-gfgr (critical): Authenticated low-priv user can become superAdmin via PATCH /user/<id>/groups/<gid> |
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 telemetry or error reporting is wired in anywhere
adequateNone of 1,063 readable files references an instrumentation, metrics or error-reporting library. If this system is in production, nobody learns that it broke from the system itself — they learn it from a customer. That is a reliability finding before it is an observability one.
| telemetry-scan | searched 1,063 tracked text files for 16 known instrumentation libraries; manifests for metrics, tracing and error-reporting families; locked dependencies for the packages that emit; 0 matched |
Respond to this finding
Your response is published beside the finding, not instead of it. A finding you can argue with is the point — and a wrong one is calibration data we want.
An owner's response is removed only when it is unlawful, impersonates someone, publishes personal data or a credential, or is not about the finding. Disagreeing with the report is never a reason. To report a response, or to reach us about one, write to takedown@borehole.dev.
No structured logging library is in use
adequateNothing references a structured logging library. Logs that are written to be read by a person are not searchable by a machine, which means incident response here is proportional to how well someone remembers the codebase rather than to what the tooling can find.
| logging-scan | searched 1,063 files for 10 structured logging libraries; 0 matched |
Respond to this finding
Your response is published beside the finding, not instead of it. A finding you can argue with is the point — and a wrong one is calibration data we want.
An owner's response is removed only when it is unlawful, impersonates someone, publishes personal data or a credential, or is not about the finding. Disagreeing with the report is never a reason. To report a response, or to reach us about one, write to takedown@borehole.dev.
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.
1 of 4 deployments run a single replica
adequate1 deployments set `replicas: 1`, and nothing (an autoscaler, a disruption budget) adds more. Every deploy and every node drain is downtime, and the availability the buyer inherits has a ceiling.
A note that does not affect this rating: in Borehole's calibration, this check's notes were usually true but overstated.
| helm/roxy-wi/templates/deployment-scheduler.yaml | helm/roxy-wi/templates/deployment-scheduler.yaml — replicas: 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.
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 No architecture or design document is in the tree, across 727 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 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 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 (23% 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 app/, helm/, config_other/. Which of your existing systems would each of those have to absorb or replace?
- The repository carries deployment configuration (docker/Dockerfile and 18 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/roxy-wi/roxy-wi/11d6b90)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 — 65
| Signal | What it found |
|---|---|
| 04.hotspot_concentration | change is spread across the codebase rather than pooling in a few filesfiles 2,022 · top5 share 0.109 |
| 04.debt_markers | debt markers are sparsemarkers 3 · per kloc 0.02 · lines read 177,730 |
| 04.dependency_sprawl | direct dependency counts are unremarkable |
| 04.test_growth | test effort kept pace with code writtenlate test per code 0.354 · early test per code 0.0 |
| 04.churn_trend | rework is not rising against new worklate delete per insert 0.538 · early delete per insert 0.257 |
| 04.eol_runtime | every pinned runtime is still supportedeol as of 2026-09-24 |
| 04.fixes_with_tests | fixes usually come with a testfixes 31 · share 0.548 · with tests 17 |
| 04.schema_churn | columns, once added, staydropped within 90 days 0 · columns added last year 14 |
| 04.compat_layers | little code is kept for the old wayshare 0.0 · code files 438 · compat files 0 |
| 06.healthcheck_presence | a health or readiness check is defined |
| 06.print_logging | raw prints are few, or outnumbered by logger callsprints 95 · logger calls 61 |
| 06.correlation_ids | a request can be followed through the logstracing False · request id sites 2 |
| 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 1 |
| 06.environment_branching | environment differences live in configurationsites 0 |
| 06.migrate_on_start | migrations do not run at container start |
| 03.active_contributors | 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.second_contributor_attrition | withheld: this check's result would describe one person |
| 03.bus_factor_trend | withheld: this check's result would describe one person |
| 02.merge_discipline | a meaningful share of recent change carries evidence of reviewmerges 17 · window last 24 months · with tracked 0 |
| 02.ci_presence | CI configuration is present in the working treecount 4 |
| 02.test_presence | tests are present in a normal proportion to sourcetests 253 · source 676 · test ratio 0.374 |
| 02.release_cadence | tags are presenttags 123 |
| 02.branch_protection_hints | process scaffolding is present in the repository |
| 02.ci_runs_tests | CI invokes a test runnerconfigs 4 · with tests 2 |
| 02.skipped_tests | few tests are switched offfocused 0 · skipped 0 · test files 255 |
| 02.ci_test_gating | no test run in CI is written so that it cannot failconfigs 4 |
| 02.revert_share | change is rarely undoneshare 0.0 · reverts 0 · recent commits 181 |
| 02.flaky_test_markers | tests are not retried until they passtest retries 0 · suite retries 0 |
| 01.burst_import | no commit run met both the rate and the net-addition thresholdgap seconds 180 · min add ratio 3.0 · min net added 2,000 |
| 01.initial_dump | first commit is not a disproportionate share of the codebaseinsertions 268 · share of insertions 0.0007 |
| 01.revision_depth | most files were revisited after they were first writtenfiles seen 612 · write once share 0.345 |
| 01.duplicated_blocks | little shipping code is repeated verbatim across filesshare 0.016 · product files 423 · distinct blocks 71,957 |
| 01.build_reproducibility | every base image names a versionfloating 0 · from lines 2 |
| 01.unfinished_migration | no language migration is stalled halfway |
| 01.weights_in_git | no model weights are committedfiles 0 |
| 05.committed_secrets | no credential-shaped strings outside test and fixture pathsnote the working tree only; the history is 05.5 · patterns 8 · files read 1,063 |
| 05.security_guardrails | at least one standard guard rail is configured |
| 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 1 |
| 05.secrets_management_pattern | no environment file is committed outside tests and examplesenv files 0 |
| 05.supply_chain_pinning | third-party build steps are pinned, or fewaction refs 23 · pipe to shell 0 · unpinned third party 1 |
| 05.outbound_timeouts | outbound calls set timeouts, or are fewcalls without timeout 0 |
| 05.migration_reversibility | migrations can be rolled backshare 0.0 · migrations 59 · irreversible 0 |
| 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.unsafe_deserialization | no code-executing deserialiser in product codesites 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 1 |
| 05.license_vendored_unlicensed | all 1 vendored components state their terms, in a licence file, their own headers or a notices filecomponents 1 · stated in headers or notices 1 |
| 05.license_grant_unclear | the licence is recognisable as Apache-2.0class permissive · license Apache-2.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 59 · added in two years 13 · 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 29.0 · days since last tag 10 · commits last 90 days 87 |
| 04.release_branch | the newest release was cut from the branch surveyedelsewhere 0 · on branch 34 · tags in window 34 |
| 03.single_maintainer | withheld: this check's result would describe one person |
| 05.project_exploited | no affecting advisory is on CISA's Known Exploited listexploited 0 |
Could not conclude, or did not apply — 23
Not a clean result. Each says why it could not answer here.
| Signal | Why |
|---|---|
| 04.fix_share_trend | fewer than six busy quarters to compare |
| 04.dependency_redundancy | no JavaScript manifest to read |
| 06.telemetry_depth | none at all is 06.1 |
| 06.alert_rules | no alert rules in the repository; they may live in a console |
| 06.deployed_image_floats | no deployment descriptor names an image |
| 06.release_markers | fewer than 100 commits in the last year |
| 06.feature_flags | no feature-flag service; flags may live elsewhere |
| 03.knowledge_silos | withheld: this check's result would describe one person |
| 03.joiners_and_leavers | withheld: this check's result would describe one person |
| 02.dependency_update_cadence | no lockfile to date |
| 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.known_vulnerabilities | no lockfile this survey can read, or a collector older than 0.4.0 |
| 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 |
| 05.project_advisories | could not tell whether 1 published advisory affects the surveyed code: its version could not be placed |
Anyone can check this report against the authoritative record — click the stamp, or enter 29KR-FYYR-PAT2 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/29KRFYYRPAT2?via=badge)
9 pieces of evidence on this report quote the repository directly. Four checks quote text: up to five TODO-style comments, up to four commit subjects, up to five unpinned dependency lines and one status line from the README's first screen, such as “no longer maintained”. In each case the text is the evidence, which is why it is kept by default.
This rewrites every stored reading of this repository, and every later reading, including a re-read, is stored without the quoted text. The facts we keep to re-read it still hold the lines, as the privacy notice says. The pointers stay.
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: 47.7authenticated: False |
| 3.4s | cloned the repository to a temporary directory | depth: full |
| 5.3s | read the git history | commits: 1820tracked files: 1230 |
| 65.4s | ran the deterministic checks | blame pass: Trueread working tree: False |
| 65.4s | recorded where this scan ran | attested: Falseenvironment: cloud-run |
| 104.1s | kept the facts, never the source, for re-reading under new checks | |
| 104.1s | deleting the working copy |
Total 104.1s ·source content sent off this machine: none · calls to a language model: 0 · the clone was deleted when the survey ended
An automated reading of a repository's code and its history up to one commit, with public advisory records. It may be wrong, it is not legal, financial, investment or security advice, and it does not replace diligence by a qualified person. It is provided for information: nobody may rely on it (Borehole's terms, section 3).