4871a55 · 3,887 commits · 1,360 files
Issued 2026-10-22
Nothing significant. Questions worth asking about Security & Reliability Posture, Product & Engineering Maturity.
105 checks ran across 6 assessable dimensions. 1 finding is worth checking first. 12 findings, each with evidence. One dimension cannot be assessed without an acquirer.
- 04.62 Releases are cut from another branch than the one surveyed
- 05.60 Relicensed: AGPL-3.0 → Apache-2.0 (2025-01-23) LICENSE
- states a policy on AI-generated contributions AI_POLICY.md:1
- names OpenSSF README.md:3
Borehole's proprietary scoring is calibrated across hundreds of repositories. Each finding here reads significant, but its check has not yet held up often enough in that calibration to rate significant on its own. If one holds when someone checks it, it is significant.
- 05.26 33 locked dependencies have published vulnerabilities, 3 high or critical in what ships
- 1 finding from checks Borehole's calibration found wrong more often than right is no longer published.
| Dimension | Rating | ||
|---|---|---|---|
| 01 | Architecture & Codebase — including AI provenance | strong | |
| 02 | Engineering Process & SDLC Maturity | adequate | |
| 03 | Organization & Key-Person Risk | strong | |
| 04 | Product & Engineering Maturity | adequate | |
| 05 | Security & Reliability Posture | adequate | |
| 06 | Observability & Operations | adequate | |
| 07 | Fit with the Acquirer | not assessable |
- 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
- the declared share is neither decisive nor negligible, so the true figure is more sensitive to undeclared work
- deep scan blamed 1,351 of 1,351 counted files
Architecture & Codebase — including AI provenance
01 · strong · ratings ↑quickwit/quickwit-search/src/root.rs is 5,826 lines, 34× this codebase's median file
adequateThe median source file here is 170 lines. 22 files exceed 1,700 lines, the largest being 5,826. 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 | quickwit/quickwit-search/src/root.rs:1 — 5,826 lines (34× median) |
| line-count | quickwit/quickwit-control-plane/src/ingest/ingest_controller.rs:1 — 4,202 lines (24× median) |
| line-count | quickwit/quickwit-ingest/src/ingest_v2/ingester.rs:1 — 3,645 lines (21× median) |
| line-count | quickwit/quickwit-search/src/leaf.rs:1 — 3,284 lines (19× median) |
| line-count | quickwit/quickwit-control-plane/src/control_plane.rs:1 — 2,895 lines (17× median) |
Respond to this finding
Your response is published beside the finding, not instead of it. A finding you can argue with is the point — and a wrong one is calibration data we want.
An owner's response is removed only when it is unlawful, impersonates someone, publishes personal data or a credential, or is not about the finding. Disagreeing with the report is never a reason. To report a response, or to reach us about one, write to takedown@borehole.dev.
Engineering Process & SDLC Maturity
02 · adequate · ratings ↑5% of recent commits change more than 2,000 lines
adequate30 of 552 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 | 30 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 · strong · ratings ↑No finding. 10 checks ran and none fired; the rejection log below says why each did not.
Product & Engineering Maturity
04 · adequate · ratings ↑14% of bug fixes add or change a test
adequateOf 131 fixes in the last 24 months, 18 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 | 18 of 131 |
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 release, v0.9.3, is not on the branch this survey read; the newest release on it is v0.9.0. 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.
| 15e3429ec | tag v0.9.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.
Security & Reliability Posture
05 · adequate · ratings ↑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 | Dockerfile — runs as root |
| no-USER-instruction | distribution/docker/ubuntu/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.
33 locked dependencies have published vulnerabilities, 3 high or critical in what ships
adequate worth checking first33 of 1,926 locked dependencies match 72 published advisories in OSV, 26 of them rated high or critical. A lockfile says which version is installed, not whether the flawed code is reachable from this product, so each needs a look. Most are fixed by an upgrade, and the advisory names the version. This lockfile pins development tools alongside what ships and does not say which is which, so some of these may never reach a user.
The check that found this reads significant, but it has not yet held up often enough in Borehole's calibration to rate a finding significant on its own. Opening quickwit/rest-api-tests/Pipfile.lock and the 1 other file it cites settles it. If it holds when someone checks it, this finding is significant.
| quickwit/rest-api-tests/Pipfile.lock | quickwit/rest-api-tests/Pipfile.lock — certifi 2026.2.25: GHSA-6q48-6c7w-9gw2 (critical), fixed in 2026.10.19 |
| quickwit/quickwit-ui/yarn.lock | quickwit/quickwit-ui/yarn.lock — dompurify 3.4.14: GHSA-cg2g-xh64-v4q7 (critical), fixed in 3.4.17 |
| quickwit/rest-api-tests/Pipfile.lock | quickwit/rest-api-tests/Pipfile.lock — urllib3 2.7.0: GHSA-8988-9cw3-xx77 (high), fixed in 2.8.0 |
Respond to this finding
Your response is published beside the finding, not instead of it. A finding you can argue with is the point — and a wrong one is calibration data we want.
An owner's response is removed only when it is unlawful, impersonates someone, publishes personal data or a credential, or is not about the finding. Disagreeing with the report is never a reason. To report a response, or to reach us about one, write to takedown@borehole.dev.
The build runs third-party code it does not pin
adequate4 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/publish_docker_images.yml | .github/workflows/publish_docker_images.yml:47 — 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.
3 deserialisers that can run code
adequate3 places read data with a deserialiser that executes what it reads (`yaml.load` without a safe loader). That is safe on data the system wrote itself and remote code execution on anything else. Ask where each one's input comes from.
A note that does not affect this rating: in Borehole's calibration, this check's notes were usually true but overstated.
| quickwit/rest-api-tests/run_tests.py | quickwit/rest-api-tests/run_tests.py:33 — code-executing deserialiser |
| quickwit/rest-api-tests/run_tests.py | quickwit/rest-api-tests/run_tests.py:66 — code-executing deserialiser |
| quickwit/rest-api-tests/run_tests.py | quickwit/rest-api-tests/run_tests.py:286 — code-executing deserialiser |
Respond to this finding
Your response is published beside the finding, not instead of it. A finding you can argue with is the point — and a wrong one is calibration data we want.
An owner's response is removed only when it is unlawful, impersonates someone, publishes personal data or a credential, or is not about the finding. Disagreeing with the report is never a reason. To report a response, or to reach us about one, write to takedown@borehole.dev.
Relicensed: AGPL-3.0 → Apache-2.0 (2025-01-23)
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".
| c8f03d4fb | LICENSE — AGPL-3.0 from 2021-04-13 |
| 3bb278160 | LICENSE — Apache-2.0 from 2025-01-23 |
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 advisories against this project in the last 24 months, 2 high or critical
adequateThe newest was published on 2026-10-16. 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 2 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 0.9.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-g85h-2988-4cv8 | 2026-10-16: GHSA-g85h-2988-4cv8 (critical), fixed in 0.9.2: Unauthenticated remote command execution via Kafka source client_params in Linux release binaries |
| GHSA-55pj-w5q5-r3m6 | 2026-09-23: GHSA-55pj-w5q5-r3m6 (high), fixed in 0.9.1: Unauthenticated denial of service via unbounded trace search 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.
Observability & Operations
06 · adequate · ratings ↑One request cannot be followed through the logs
adequateNothing in the service carries a request or correlation id, and there is no tracing. When a customer reports a failure, the log lines that belong to their request cannot be picked out from everyone else's.
| request ids | no request id, correlation id or tracing found |
Respond to this finding
Your response is published beside the finding, not instead of it. A finding you can argue with is the point — and a wrong one is calibration data we want.
An owner's response is removed only when it is unlawful, impersonates someone, publishes personal data or a credential, or is not about the finding. Disagreeing with the report is never a reason. To report a response, or to reach us about one, write to takedown@borehole.dev.
No error reporter is wired in
adequateNothing in the service initialises an error reporter (Sentry, Rollbar, Bugsnag, Honeybadger or an APM agent). An exception in production reaches a person only if someone is reading the logs, which usually means a customer reports it first.
A note that does not affect this rating: notes like it are common in well-run projects.
| error reporting | no error reporter initialised |
Respond to this finding
Your response is published beside the finding, not instead of it. A finding you can argue with is the point — and a wrong one is calibration data we want.
An owner's response is removed only when it is unlawful, impersonates someone, publishes personal data or a credential, or is not about the finding. Disagreeing with the report is never a reason. To report a response, or to reach us about one, write to takedown@borehole.dev.
Fit with the Acquirer
07 · not assessable · ratings ↑Not rated: structurally not assessable from a repository. What a person adds here.
Check it on the running system
5 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/overview/architecture.md and 1 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 coverage- measured 120 people have committed here. Which of them are you acquiring, and which are you replacing?
- Who mentors whom, and would that survive a departure?
- Can the team grow, and who stands behind the top three contributors?
- Is the seniority mix sound, and will pay survive your salary bands?
- Is the pace sustainable? Commit times cannot say: git keeps no reliable local time.
- Does the team want to stay after close?
- How are decisions made and disagreements resolved?
Product & Engineering Maturity
04 · minimal coverage- measured 439 commits landed in the last year, against 194 the year before (+126%). 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 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 (distribution/ecs/quickwit/cluster.tf and 14 more) last changed 21 months before the newest commit, while 590 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 Rust codebase. Does your engineering organisation already run Rust in production, or would this be the first?
- The bulk of this system sits in quickwit/, distribution/, monitoring/. Which of your existing systems would each of those have to absorb or replace?
- 45% of lines added in the last 12 months (11% of added lines) came through AI-declared commits. Does your organisation have a policy on inheriting and maintaining that code, and does your engineering team's tooling match how it was produced?
- The repository carries deployment configuration (Dockerfile and 4 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/quickwit-oss/quickwit/4871a55)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 — 93 signals that ran and did not fire
Appendix: rejection log — 93 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 — 67
| Signal | What it found |
|---|---|
| 04.hotspot_concentration | change is spread across the codebase rather than pooling in a few filesfiles 3,885 · top5 share 0.035 |
| 04.debt_markers | debt markers are sparsemarkers 229 · per kloc 0.66 · lines read 345,840 |
| 04.dependency_sprawl | direct dependency counts are unremarkable |
| 04.churn_trend | rework is not rising against new worklate delete per insert 0.372 · early delete per insert 0.454 |
| 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 10 |
| 04.compat_layers | little code is kept for the old wayshare 0.0 · code files 757 · compat files 0 |
| 04.dependency_redundancy | one library per job, mostly |
| 06.telemetry_presence | a telemetry or error-reporting library is referencednote presence only; whether anyone watches it is not visible here · matches 807 |
| 06.healthcheck_presence | a health or readiness check is defined |
| 06.usage_reporting_default | the product's code names no reporting hostsettings on 2 · settings off 0 |
| 06.deployed_image_floats | every deployed image names a versionimages 15 · floating 0 |
| 06.release_markers | releases are markedtags last year 27 · release commits 2 · changelog commits 6 |
| 06.migrate_on_start | migrations do not run at container start |
| 03.contributor_concentration | no single contributor dominates the last 24 monthsyears 5.5 · window last 24 months · authors 120 |
| 03.active_contributors | more than one contributor active in the trailing yearall time 120 · active 12mo 31 |
| 03.knowledge_silos | every substantial directory has been touched by more than one personauthors 120 · directories 3 |
| 03.drive_by_contributors | an open contributor base, where one-commit contributors are normalauthors 120 · one off share 0.475 |
| 03.contributor_attrition | no contributor dominates enough for their absence to matterauthors 120 · top share less than a quarter · top contributor last committed within the last three months |
| 03.critical_path_ownership | more than one person changes the critical pathsauthors 48 |
| 03.second_contributor_attrition | the second and third contributors are still active |
| 03.bus_factor_trend | the team has not narrowed to one person |
| 03.joiners_and_leavers | the team is not shrinkingleft 1 · joined 14 · regular last year 21 |
| 02.merge_discipline | a meaningful share of recent change carries evidence of reviewmerges 0 · window last 24 months · with tracked 9 |
| 02.ci_presence | CI configuration is present in the working treecount 14 |
| 02.test_presence | tests are present in a normal proportion to sourcetests 424 · source 806 · test ratio 0.526 |
| 02.release_cadence | tags are presenttags 236 |
| 02.conventional_commits | commit subjects generally carry contentsampled 3,863 · low content share 0.011 |
| 02.branch_protection_hints | process scaffolding is present in the repository |
| 02.ci_runs_tests | CI invokes a test runnerconfigs 13 · with tests 3 |
| 02.skipped_tests | few tests are switched offfocused 0 · skipped 3 · test files 105 |
| 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.002 · reverts 1 · recent commits 636 |
| 02.dependency_update_cadence | dependencies move with the codelockfiles 4 · commits since 1 · days since lockfile changed 0 |
| 02.flaky_test_markers | tests are not retried until they passtest retries 0 · suite retries 0 |
| 02.lint_in_build | a linter or formatter runs in the buildwired 3 · ci configs 14 · product files 757 |
| 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 672 · share of insertions 0.0007 |
| 01.message_uniformity | commit subjects vary in wording and lengthlength stdev 18.37 · repeat share 0.016 |
| 01.revision_depth | most files were revisited after they were first writtenfiles seen 1,029 · write once share 0.192 |
| 01.duplicated_blocks | little shipping code is repeated verbatim across filesshare 0.0026 · product files 729 · distinct blocks 179,235 |
| 01.build_reproducibility | every base image names a versionfloating 0 · from lines 5 |
| 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,246 |
| 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.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.source_maps_shipped | production builds do not publish source mapssites 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 24 |
| 05.license_vendored_unlicensed | all 4 vendored components state their terms, in a licence file, their own headers or a notices filecomponents 4 · stated in headers or notices 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 3 |
| 04.dependency_churn | few dependencies were added and dropped within 60 daysdependencies seen 368 · added in two years 91 · removed within 60 days 4 |
| 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 0.0 · days since last tag 0 · commits last 90 days 136 |
| 03.single_maintainer | no file says one person maintains itstatements 0 |
Could not conclude, or did not apply — 26
Not a clean result. Each says why it could not answer here.
| Signal | Why |
|---|---|
| 04.test_growth | Rust keeps unit tests inside the files they test, which a count by file name cannot see |
| 06.structured_logging | not assessed for Rust: its logging setup is not read |
| 06.telemetry_depth | none at all is 06.1 |
| 06.print_logging | a frontend: console output is the browser's, not the server's |
| 06.alert_rules | no alert rules in the repository; they may live in a console |
| 06.probes_identical | no Kubernetes probes |
| 06.single_replica | no Kubernetes deployments |
| 06.environment_branching | not assessed for Rust, the language the product is written in: this check's patterns read other languages only |
| 06.feature_flags | no feature-flag service; flags may live elsewhere |
| 02.long_lived_branches | too few merges to judge (squash and rebase leave none) |
| 01.swallowed_errors | not assessed for Rust, 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 Rust, 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 Rust, the language the product is written in: this check's patterns read other languages only |
| 05.shell_from_strings | not assessed for Rust, the language the product is written in: this check's patterns read other languages only |
| 05.tls_verification_off | not assessed for Rust, the language the product is written in: this check's patterns read other languages only |
| 05.resource_limits | no Kubernetes workload manifests |
| 05.public_env_secret | not assessed for Rust, the language the product is written in: this check's patterns read other languages only |
| 05.unsafe_html | not assessed for Rust, the language the product is written in: this check's patterns read other languages only |
| 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 |
| 05.project_advisories | record incomplete: no advisory found in the sources that answered; OSV crates.io quickwit-actors (an empty record for a package published here), OSV crates.io quickwit-aws (an empty record for a package published here), OSV crates.io quickwit-cluster (an empty record for a package published here), OSV crates.io quickwit-common (an empty record for a package published here), OSV crates.io quickwit-config (an empty record for a package published here), OSV crates.io quickwit-directories (an empty record for a package published here), OSV crates.io quickwit-doc-mapper (an empty record for a package published here), OSV crates.io quickwit-indexing (an empty record for a package published here), OSV crates.io quickwit-metastore (an empty record for a package published here), NVD did not |
| 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 0F8E-WT8D-5QQJ 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/0F8EWT8D5QQJ?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: 88.8authenticated: False |
| 9.4s | cloned the repository to a temporary directory | depth: full |
| 15.7s | read the git history | commits: 3887tracked files: 1360 |
| 183.3s | ran the deterministic checks | blame pass: Trueread working tree: False |
| 183.3s | recorded where this scan ran | attested: Falseenvironment: cloud-run |
| 210.4s | kept the facts, never the source, for re-reading under new checks | |
| 210.4s | deleting the working copy |
Total 210.4s ·source content sent off this machine: none · calls to a language model: 0 · the clone was deleted when the survey ended
An automated reading of a repository's code and its history up to one commit, with public advisory records. It may be wrong, it is not legal, financial, investment or security advice, and it does not replace diligence by a qualified person. It is provided for information: nobody may rely on it (Borehole's terms, section 3).