6ce51ac · 18,695 commits · 1,296 files
Issued 2026-10-23
Reads strong: 4 of 6 rated dimensions are strong, 2 are adequate and none is significant.
105 checks ran across 6 assessable dimensions. Security & Reliability Posture and Architecture & Codebase — including AI provenance are adequate. 11 findings, each with evidence. One dimension cannot be assessed without an acquirer.
This repository reads strong. Show it in your README: the badge links to a page where anyone can check the reading. 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/FQ22TBDZDZHK?via=badge)- names CNCF README.md:28
- 1 finding from checks Borehole's calibration found wrong more often than right is no longer published.
- 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 | adequate | |
| 02 | Engineering Process & SDLC Maturity | strong | |
| 03 | Organization & Key-Person Risk | strong | |
| 04 | Product & Engineering Maturity | strong | |
| 05 | Security & Reliability Posture | adequate | |
| 06 | Observability & Operations | strong | |
| 07 | Fit with the Acquirer | not assessable |
- 22% 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,277 of 1,277 counted files
Architecture & Codebase — including AI provenance
01 · adequate · ratings ↑5 base images float: no version, or `latest`
adequate5 of 7 `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.
| docker/apiext/Dockerfile | docker/apiext/Dockerfile:3 — base image without a version |
| docker/emissary/Dockerfile | docker/emissary/Dockerfile:90 — base image without a version |
| docker/kat-client/Dockerfile | docker/kat-client/Dockerfile:3 — 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.
python/ambassador-diag/src/ambassador_diag/diagd.py is 2,346 lines, 19× this codebase's median file
adequateThe median source file here is 119 lines. 6 files exceed 1,190 lines, the largest being 2,346. 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 | python/ambassador-diag/src/ambassador_diag/diagd.py:1 — 2,346 lines (19× median) |
| line-count | python/kat/src/kat/harness.py:1 — 1,809 lines (15× median) |
| line-count | python/ambassador/src/ambassador/envoy/v3/v3listener.py:1 — 1,308 lines (10× median) |
| line-count | python/ambassador/src/ambassador/utils.py:1 — 1,273 lines (10× median) |
| line-count | python/ambassador/src/ambassador/ir/ir.py:1 — 1,268 lines (10× 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 · strong · ratings ↑No finding. 16 checks ran and none fired; the rejection log below says why each did not.
Organization & Key-Person Risk
03 · strong · ratings ↑No finding. 10 checks ran and none fired; the rejection log below says why each did not.
Product & Engineering Maturity
04 · strong · ratings ↑No finding. 19 checks ran and none fired; the rejection log below says why each did not.
Security & Reliability Posture
05 · adequate · ratings ↑9 credential-shaped strings in the tree sit in tests, examples, documentation or local development settings
adequateStrings shaped like credentials appear only where fakes are usual: test fixtures, examples, documentation, placeholders and local stacks. They are almost always fakes. Ask someone to confirm that none of them works anywhere, because a real key in a development file is still a real key.
| private key block | 5 cited: private key block, where fakes are usual |
| 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.
None of the standard security guard rails are configured
adequateThere is no disclosure policy, no automated dependency updates, no named code owners and no pre-commit configuration. None of these is load-bearing on its own. Their collective absence says that security posture here is whatever the current team happens to remember to do, which is not a posture that survives the team changing.
| guardrail-scan | checked 5 kinds of guard rail across 1,296 tracked files; 0 present |
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 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 | docker/emissary/Dockerfile — runs as root |
| no-USER-instruction | docker/kat-server/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.
The build runs third-party code it does not pin
adequate7 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; 2 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.
| .github/workflows/build-images.yaml | .github/workflows/build-images.yaml:113 — action pinned by tag |
| .github/workflows/build-images.yaml | .github/workflows/build-images.yaml:119 — action pinned by tag |
| .github/workflows/deprecated/execute-tests-and-promote.yml | .github/workflows/deprecated/execute-tests-and-promote.yml:164 — 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.
5 outbound calls can wait forever
adequate5 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.
| python/ambassador-diag/src/ambassador_diag/diagd.py | python/ambassador-diag/src/ambassador_diag/diagd.py:1032 — outbound call without a timeout |
| python/ambassador/src/ambassador/diagnostics/envoy_stats.py | python/ambassador/src/ambassador/diagnostics/envoy_stats.py:179 — outbound call without a timeout |
| python/ambassador/src/ambassador/diagnostics/envoy_stats.py | python/ambassador/src/ambassador/diagnostics/envoy_stats.py:193 — 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.
9 shell commands built from strings
adequate9 places run a command through a shell (`shell=True`, `os.system`, `exec` with a template) rather than passing arguments. Where any part comes from outside, it is command injection. Ask where each one's input comes from.
A note that does not affect this rating: in Borehole's calibration, this check's notes were usually true but overstated.
| python/ambassador-diag/src/ambassador_diag/diagd.py | python/ambassador-diag/src/ambassador_diag/diagd.py:1764 — command run through a shell |
| python/kat/src/kat/harness.py | python/kat/src/kat/harness.py:62 — command run through a shell |
| python/kat/src/kat/harness.py | python/kat/src/kat/harness.py:68 — command run through 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.
2 locked dependencies have published vulnerabilities
adequate2 of 175 locked dependencies match 6 published advisories in OSV. 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.
A note that does not affect this rating: in Borehole's calibration, this check's notes were usually true but overstated.
| go.mod | go.mod — github.com/gorilla/websocket v1.5.1: GHSA-w67g-5rqw-f597 (moderate), fixed in 1.5.3 |
| go.mod | go.mod — k8s.io/kubernetes v1.30.3: GHSA-3wgm-2gw2-vh5m (moderate) |
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 · strong · ratings ↑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 2 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.
| charts/emissary-ingress/values.yaml | charts/emissary-ingress/values.yaml:23 — 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 (DevDocumentation/ARCHITECTURE.md). 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 coverage- measured 260 people have committed here. Which of them are you acquiring, and which are you replacing?
- measured The repository went quiet for 10 months, from October 2024 to August 2025, then 63 commits landed in the six weeks after. Where was the work of that period done, and is it in this history? The history shows the gap, not why it happened.
- 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- measured 188 commits landed in the last year, against 66 the year before (+185%). What drove it: new people, a deadline, or code produced faster than before?
- 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?
- measured Infrastructure code (charts/emissary-crds/Chart.yaml and 1 more) last changed 13 months before the newest commit, while 198 commits landed. Is the infrastructure now changed by hand? Compare the live account with the code.
- What has actually broken, how often, and how badly?
- What did external testing find, and was it fixed?
- What is the SOC 2, ISO 27001 or GDPR status, and where is the evidence?
Observability & Operations
06 · partial coverage- measured Nothing in the tree backs up or restores data. How is data backed up, and has a restore ever been rehearsed?
- measured No alert rule is defined in the repository. Where are alerts defined, who receives them, and when did one last fire?
- Are the dashboards opened, the alerts acknowledged and the pages answered?
- Are the service-level objectives actually met?
- Who carries the pager, and how often does it go off?
- What does it cost to run, and how much headroom is there?
Fit with the Acquirer
07 · none coverageNot rated: structurally not assessable from a repository.
- This is primarily a Go codebase, with Python alongside (36% of source files). Does your engineering organisation already run Go in production, or would this be the first?
- The bulk of this system sits in pkg/, python/, api/. Which of your existing systems would each of those have to absorb or replace?
- The repository carries deployment configuration (docker/apiext/Dockerfile and 12 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/emissary-ingress/emissary/6ce51ac)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 — 94 signals that ran and did not fire
Appendix: rejection log — 94 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 — 75
| Signal | What it found |
|---|---|
| 04.hotspot_concentration | change is spread across the codebase rather than pooling in a few filesfiles 30,053 · top5 share 0.017 |
| 04.debt_markers | debt markers are sparsemarkers 280 · per kloc 1.4 · lines read 200,363 |
| 04.dependency_sprawl | direct dependency counts are unremarkable |
| 04.test_growth | test effort kept pace with code writtenlate test per code 0.171 · early test per code 0.151 |
| 04.churn_trend | rework is not rising against new worklate delete per insert 0.574 · early delete per insert 0.468 |
| 04.eol_runtime | every pinned runtime is still supportedeol as of 2026-09-24 |
| 04.fixes_with_tests | fixes usually come with a testfixes 74 · share 0.297 · with tests 22 |
| 04.compat_layers | little code is kept for the old wayshare 0.0 · code files 283 · 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 46 |
| 06.structured_logging | a structured logging library is referencedmatches 13 |
| 06.healthcheck_presence | a health or readiness check is defined |
| 06.telemetry_depth | the service is visible in more than one way |
| 06.print_logging | raw prints are few, or outnumbered by logger callsprints 69 · logger calls 515 |
| 06.correlation_ids | a request can be followed through the logstracing True · request id sites 11 |
| 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 3 |
| 06.single_replica | an autoscaler or disruption budget is definedworkloads 8 |
| 06.environment_branching | environment differences live in configurationsites 0 |
| 06.release_markers | releases are markedtags last year 12 · release commits 0 · changelog commits 29 |
| 06.migrate_on_start | migrations do not run at container start |
| 03.contributor_concentration | no single contributor dominates the last 24 monthsyears 9.6 · window last 24 months · authors 260 |
| 03.active_contributors | more than one contributor active in the trailing yearall time 260 · active 12mo 11 |
| 03.knowledge_silos | every substantial directory has been touched by more than one personauthors 260 · directories 9 |
| 03.drive_by_contributors | an open contributor base, where one-commit contributors are normalauthors 260 · one off share 0.319 |
| 03.contributor_attrition | the dominant contributor is still activeauthors 260 · top share a quarter or more · top contributor last committed within the last three months |
| 03.critical_path_ownership | more than one person changes the critical pathsauthors 14 |
| 03.second_contributor_attrition | the second and third contributors are still active |
| 03.bus_factor_trend | the team has not narrowed to one person |
| 02.merge_discipline | a meaningful share of recent change carries evidence of reviewmerges 99 · window last 24 months · with tracked 2 |
| 02.ci_presence | CI configuration is present in the working treecount 14 |
| 02.test_presence | tests are present in a normal proportion to sourcetests 194 · source 467 · test ratio 0.415 |
| 02.release_cadence | tags are presenttags 912 |
| 02.conventional_commits | commit subjects generally carry contentsampled 13,626 · low content share 0.042 |
| 02.branch_protection_hints | process scaffolding is present in the repository |
| 02.ci_runs_tests | CI invokes a test runnerconfigs 14 · with tests 5 |
| 02.skipped_tests | few tests are switched offfocused 0 · skipped 0 · test files 776 |
| 02.ci_test_gating | no test run in CI is written so that it cannot failconfigs 14 |
| 02.revert_share | change is rarely undoneshare 0.0 · reverts 0 · recent commits 254 |
| 02.dependency_update_cadence | dependencies move with the codelockfiles 7 · commits since 1 · days since lockfile changed 5 |
| 02.flaky_test_markers | tests are not retried until they passtest retries 3 · suite retries 0 |
| 02.lint_in_build | a linter or formatter runs in the buildwired 5 · ci configs 14 · product files 283 |
| 02.long_lived_branches | the typical branch reaches the trunk quicklyshare 0.143 · merges 84 · long lived 12 |
| 02.commit_size | changes arrive in reviewable sizesshare 0.01 · commits 194 · over 2000 lines 2 |
| 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 565 · share of insertions 0.0 |
| 01.message_uniformity | commit subjects vary in wording and lengthlength stdev 26.0 · repeat share 0.292 |
| 01.revision_depth | most files were revisited after they were first writtenfiles seen 381 · write once share 0.244 |
| 01.duplicated_blocks | little shipping code is repeated verbatim across filesshare 0.0214 · product files 273 · distinct blocks 29,802 |
| 01.swallowed_errors | errors are rarely thrown awayloc 201,565 · files 6 · per kloc 0.05 |
| 01.unfinished_migration | no language migration is stalled halfway |
| 01.weights_in_git | no model weights are committedfiles 0 |
| 05.dependency_pinning | dependencies are substantially pinnedunpinned 3 |
| 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.sql_from_strings | no SQL is assembled from strings in product codefiles 0 · sites 0 · value interpolated 0 |
| 05.unsafe_deserialization | no code-executing deserialiser in product codesites 0 |
| 05.tls_verification_off | no TLS verification is switched off in product codefiles 0 · sites 0 · pinned instead 0 |
| 05.resource_limits | every workload declares limitsworkloads 10 · without limits 0 |
| 05.privileged_workloads | no workload runs privileged or in the host's namespacessites 0 · behind a setting or built here 0 |
| 05.credentials_in_deploy_config | deployment configuration references secrets, never holds themfiles 0 · sites 0 |
| 05.signing_material | no signing keystore or profile is committedfiles 0 |
| 05.license_vendored_unlicensed | no vendored third-party code is committedcomponents 0 |
| 05.license_grant_unclear | the licence is recognisable as Apache-2.0class permissive · license Apache-2.0 |
| 05.committed_native_libraries | no widely used compiled library is committed to the productlibraries 0 |
| 04.api_versions_coexisting | one API version is served, or none |
| 04.deprecations_lingering | few deprecations have outlived two yearsolder than two years 0 · files with deprecations 400 |
| 04.dependency_churn | few dependencies were added and dropped within 60 daysdependencies seen 389 · added in two years 33 · 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.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 8.0 · days since last tag 157 · commits last 90 days 135 |
| 04.release_branch | the newest release was cut from the branch surveyedelsewhere 57 · on branch 603 · tags in window 660 |
| 03.single_maintainer | no file says one person maintains itstatements 0 |
Could not conclude, or did not apply — 19
Not a clean result. Each says why it could not answer here.
| Signal | Why |
|---|---|
| 04.fix_share_trend | fewer than six busy quarters to compare |
| 04.schema_churn | no schema migrations to read |
| 04.dependency_redundancy | no JavaScript manifest to read |
| 06.alert_rules | no alert rules in the repository; they may live in a console |
| 06.feature_flags | no feature-flag service; flags may live elsewhere |
| 03.joiners_and_leavers | too few regular contributors to see a trend |
| 01.notebook_outputs | not a data or machine-learning repository |
| 05.migration_reversibility | too few migrations to judge |
| 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 |
| 05.project_advisories | record incomplete: no advisory found in the sources that answered; OSV Go github.com/emissary-ingress/emissary/v3 (an empty record for a package published here) did not; NVD: 15 records name emissary with nothing tying them to this repository (CVE-2021-32092, CVE-2021-32093, CVE-2021-32094, …) |
| 05.advisory_record | record incomplete: no advisory against the project in the last 24 months; OSV Go github.com/emissary-ingress/emissary/v3 (an empty record for a package published here) did not answer; NVD: 15 records name emissary with nothing tying them to this repository (CVE-2021-32092, CVE-2021-32093, CVE-2021-32094, …) |
| 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 FQ22-TBDZ-DZHK 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/FQ22TBDZDZHK?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: 122.1authenticated: False |
| 16.4s | cloned the repository to a temporary directory | depth: full |
| 38.1s | read the git history | commits: 18695tracked files: 1296 |
| 312.3s | ran the deterministic checks | blame pass: Trueread working tree: False |
| 312.3s | recorded where this scan ran | attested: Falseenvironment: cloud-run |
| 448.1s | kept the facts, never the source, for re-reading under new checks | |
| 448.1s | deleting the working copy |
Total 448.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).