a6e357a · 972 commits · 1,099 files
Issued 2026-10-23
FSL-1.1-ALv2 since 2026-02-04: source available, not open source; a competing commercial product or service is not allowed; each version becomes Apache-2.0 two years after its release.
104 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.
- 05.60 FSL-1.1-ALv2 since 2026-02-04: source available, not open source; a competing commercial product or service is not allowed; each version becomes Apache-2.0 two years after its release
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 39 locked dependencies have published vulnerabilities, 8 high or critical in what ships
- 2 findings from checks Borehole's calibration found wrong more often than right are no longer published.
| Dimension | Rating | ||
|---|---|---|---|
| 01 | Architecture & Codebase — including AI provenance | strong | |
| 02 | Engineering Process & SDLC Maturity | adequate | |
| 03 | Organization & Key-Person Risk | adequate | |
| 04 | Product & Engineering Maturity | strong | |
| 05 | Security & Reliability Posture | adequate | |
| 06 | Observability & Operations | adequate | |
| 07 | Fit with the Acquirer | not assessable |
- 14% of non-merge commits carry any trailer at all
- low trailer coverage: the convention may not be in consistent use
- no widespread author/committer date divergence
- deep scan blamed 1,098 of 1,098 counted files
Architecture & Codebase — including AI provenance
01 · strong · ratings ↑No finding. 11 checks ran and none fired; the rejection log below says why each did not.
Engineering Process & SDLC Maturity
02 · adequate · ratings ↑Nothing in the history is tagged as a release
adequateAcross 5.2 years of history there is not one tag. There may still be a deployment process, but this repository holds no record of what shipped when — which is the record a buyer needs to reconstruct an incident or a regression after the fact.
| tag-list | 0 tags across 972 commits and 1903 days |
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.
Tests are retried until they pass
adequateThe suite is configured to retry failing tests (playwright.config.ts). A retry turns a flaky test green without saying why it failed, so a green build means the tests passed eventually. Ask how many retries a typical run needs, and which tests need them.
A note that does not affect this rating: notes like it are common in well-run projects.
| playwright.config.ts | playwright.config.ts:15 — test retry |
Respond to this finding
Your response is published beside the finding, not instead of it. A finding you can argue with is the point — and a wrong one is calibration data we want.
An owner's response is removed only when it is unlawful, impersonates someone, publishes personal data or a credential, or is not about the finding. Disagreeing with the report is never a reason. To report a response, or to reach us about one, write to takedown@borehole.dev.
Organization & Key-Person Risk
03 · adequate · ratings ↑Bus factor 1: recent work is concentrated in one contributor
adequateIn the last 24 months, one contributor authored more than half of 100 non-merge commits among 19 authors; across all history, less than a quarter of 915. This is the single most expensive thing to discover after closing, and the repository cannot tell you whether that person is part of the transaction.
| git shortlog -sn | last 24 months: top author more than half of 100 commits; bus factor 1; 19 authors |
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.
One person alone changes database migrations
adequateIn the last 24 months, of 19 contributors, a single person made every change to: database migrations (10 commits). These are the parts where a mistake is expensive and where knowledge is hardest to rebuild. Ask who else could change them safely tomorrow.
| git log -- <area> | sole author over 24 months: database migrations (10 commits) |
Respond to this finding
Your response is published beside the finding, not instead of it. A finding you can argue with is the point — and a wrong one is calibration data we want.
An owner's response is removed only when it is unlawful, impersonates someone, publishes personal data or a credential, or is not about the finding. Disagreeing with the report is never a reason. To report a response, or to reach us about one, write to takedown@borehole.dev.
The next contributor after the top one has not committed here for more than a year
adequateThe #2 contributor of the last three years (less than a quarter of the commits) has not committed here for more than two years, while the repository is still active. These are the people a buyer assumes would step up if the top contributor stopped. The history shows only that no commits of theirs landed here, not why.
| git shortlog -sn | the #2 contributor of the last three years (less than a quarter of the commits) has not committed here for more than two years |
Respond to this finding
Your response is published beside the finding, not instead of it. A finding you can argue with is the point — and a wrong one is calibration data we want.
An owner's response is removed only when it is unlawful, impersonates someone, publishes personal data or a credential, or is not about the finding. Disagreeing with the report is never a reason. To report a response, or to reach us about one, write to takedown@borehole.dev.
Product & Engineering Maturity
04 · 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 ↑39 locked dependencies have published vulnerabilities, 8 high or critical in what ships
adequate worth checking first39 of 995 locked dependencies match 90 published advisories in OSV, 58 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.
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 pnpm-lock.yaml settles it. If it holds when someone checks it, this finding is significant.
| pnpm-lock.yaml | pnpm-lock.yaml — shell-quote 1.8.3: GHSA-w7jw-789q-3m8p (critical), fixed in 1.8.4; a development dependency |
| pnpm-lock.yaml | pnpm-lock.yaml — browserslist 4.28.1: GHSA-73wf-gq98-2v4g (high), fixed in 4.28.7 |
| pnpm-lock.yaml | pnpm-lock.yaml — browserslist 4.28.2: GHSA-73wf-gq98-2v4g (high), fixed in 4.28.7 |
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: BSD-3-Clause → FSL-1.1-ALv2 (2026-02-04)
adequateThe root licence changed 1 time(s). The latest terms restrict what users, hosts or a buyer may do in ways the earlier ones did not. Code taken under the old terms stays under them, so both matter in diligence.
| 42d4629fb | LICENSE — BSD-3-Clause from 2022-08-02 |
| d4b1085c1 | LICENSE — FSL-1.1-ALv2 from 2026-02-04 |
Respond to this finding
Your response is published beside the finding, not instead of it. A finding you can argue with is the point — and a wrong one is calibration data we want.
An owner's response is removed only when it is unlawful, impersonates someone, publishes personal data or a credential, or is not about the finding. Disagreeing with the report is never a reason. To report a response, or to reach us about one, write to takedown@borehole.dev.
The licence is FSL-1.1-ALv2: source available, not open source
adequateLICENSE grants FSL-1.1-ALv2: source available, not open source; a competing commercial product or service is not allowed; each version becomes Apache-2.0 two years after its release. The reading comes from the licence's own title and clauses. Whether the terms fit the buyer's intended use, and whether any paid licence transfers with the code, is a question for counsel and the licensor.
A note that does not affect this rating: it names the project's licence, a fact for the first screen rather than a weakness.
| LICENSE | LICENSE:1 — 105 lines, FSL-1.1-ALv2 |
Respond to this finding
Your response is published beside the finding, not instead of it. A finding you can argue with is the point — and a wrong one is calibration data we want.
An owner's response is removed only when it is unlawful, impersonates someone, publishes personal data or a credential, or is not about the finding. Disagreeing with the report is never a reason. To report a response, or to reach us about one, write to takedown@borehole.dev.
Observability & Operations
06 · adequate · ratings ↑No telemetry or error reporting is wired in anywhere
adequateNone of 1,022 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,022 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,022 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.
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
7 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/adr/0001-locale-channel-url-routing.md and 7 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 54 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 87 commits landed in the last year, against 13 the year before (+569%). 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?
- 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 TypeScript codebase. Does your engineering organisation already run TypeScript in production, or would this be the first?
- The bulk of this system sits in src/, skills/, messages/. Which of your existing systems would each of those have to absorb or replace?
- 38% of lines added in the last 12 months (4% 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 1 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/saleor/storefront/a6e357a)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 — 92 signals that ran and did not fire
Appendix: rejection log — 92 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 — 61
| Signal | What it found |
|---|---|
| 04.hotspot_concentration | change is spread across the codebase rather than pooling in a few filesfiles 4,260 · top5 share 0.032 |
| 04.debt_markers | debt markers are sparsemarkers 0 · per kloc 0.0 · lines read 92,416 |
| 04.dependency_sprawl | direct dependency counts are unremarkable |
| 04.test_growth | test effort kept pace with code writtenlate test per code 0.136 · early test per code 0.016 |
| 04.churn_trend | rework is not rising against new worklate delete per insert 0.349 · early delete per insert 0.625 |
| 04.eol_runtime | every pinned runtime is still supportedeol as of 2026-09-24 |
| 04.compat_layers | little code is kept for the old wayshare 0.0 · code files 662 · compat files 0 |
| 06.usage_reporting_default | the product's code names no reporting hostsettings on 0 · settings off 0 |
| 06.environment_branching | environment differences live in configurationsites 1 |
| 06.migrate_on_start | migrations do not run at container start |
| 03.active_contributors | more than one contributor active in the trailing yearall time 54 · active 12mo 14 |
| 03.drive_by_contributors | an open contributor base, where one-commit contributors are normalauthors 54 · one off share 0.5 |
| 03.contributor_attrition | no contributor dominates enough for their absence to matterauthors 54 · top share less than a quarter · top contributor last committed more than a year ago |
| 02.merge_discipline | a meaningful share of recent change carries evidence of reviewmerges 0 · window last 24 months · with tracked 2 |
| 02.ci_presence | CI configuration is present in the working treecount 5 |
| 02.test_presence | tests are present in a normal proportion to sourcetests 139 · source 801 · test ratio 0.174 |
| 02.conventional_commits | commit subjects generally carry contentsampled 916 · low content share 0.035 |
| 02.branch_protection_hints | process scaffolding is present in the repository |
| 02.ci_runs_tests | CI invokes a test runnerconfigs 5 · with tests 2 |
| 02.skipped_tests | few tests are switched offfocused 0 · skipped 0 · test files 140 |
| 02.ci_test_gating | no test run in CI is written so that it cannot failconfigs 5 |
| 02.revert_share | change is rarely undoneshare 0.0 · reverts 0 · recent commits 100 |
| 02.dependency_update_cadence | dependencies move with the codelockfiles 1 · commits since 1 · days since lockfile changed 5 |
| 02.lint_in_build | a linter or formatter runs in the buildwired 2 · ci configs 5 · product files 662 |
| 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 94,056 · share of insertions 0.0586 |
| 01.message_uniformity | commit subjects vary in wording and lengthlength stdev 16.09 · repeat share 0.049 |
| 01.revision_depth | most files were revisited after they were first writtenfiles seen 865 · write once share 0.474 |
| 01.oversized_modules | no module is an outlier against this codebase's own normlargest 2,161 · threshold 1,000 · median lines 50 |
| 01.duplicated_blocks | little shipping code is repeated verbatim across filesshare 0.0064 · product files 662 · distinct blocks 33,467 |
| 01.swallowed_errors | errors are rarely thrown awayloc 93,437 · files 0 · per kloc 0.0 |
| 01.build_reproducibility | every base image names a versionfloating 0 · from lines 3 |
| 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,022 |
| 05.security_guardrails | at least one standard guard rail is configured |
| 05.dependency_pinning | a lockfile is committed, so builds are reproduciblelockfile True |
| 05.license_present | a licence file is presentfound True |
| 05.secrets_in_history | no credential-shaped string was ever added outside test and fixture pathspatterns 8 · truncated False · added lines 1,548,316 |
| 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 14 · pipe to shell 0 · unpinned third party 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.tls_verification_off | no TLS verification is switched off in product codefiles 0 · sites 0 · pinned instead 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.public_env_secret | only publishable values carry a public prefixnames 0 · sites 0 · not secrets 0 |
| 05.unsafe_html | raw HTML is rare, literal or sanitisedsites 2 |
| 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_vendored_unlicensed | no vendored third-party code is committedcomponents 0 |
| 05.committed_native_libraries | no widely used compiled library is committed to the productlibraries 0 |
| 04.deprecations_lingering | few deprecations have outlived two yearsolder than two years 0 · files with deprecations 20 |
| 04.dependency_churn | few dependencies were added and dropped within 60 daysdependencies seen 181 · added in two years 22 · 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 |
| 03.single_maintainer | no file says one person maintains itstatements 0 |
Could not conclude, or did not apply — 31
Not a clean result. Each says why it could not answer here.
| Signal | Why |
|---|---|
| 04.fixes_with_tests | too few fixes in 24 months to judge |
| 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.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.deployed_image_floats | no deployment descriptor names an image |
| 06.probes_identical | no Kubernetes probes |
| 06.single_replica | no Kubernetes deployments |
| 06.release_markers | fewer than 100 commits in the last year |
| 06.feature_flags | no feature-flag service; flags may live elsewhere |
| 03.bus_factor_trend | fewer than three active years to compare |
| 03.joiners_and_leavers | too few regular contributors to see a trend |
| 02.long_lived_branches | too few merges to judge (squash and rebase leave none) |
| 02.commit_size | too few recent commits |
| 01.notebook_outputs | not a data or machine-learning repository |
| 05.outbound_timeouts | not assessed for TypeScript or TSX, the languages the product is written in: this check's patterns read other languages only |
| 05.migration_reversibility | too few migrations to judge |
| 05.resource_limits | no Kubernetes workload manifests |
| 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 | manifest licence 'SEE LICENSE IN LICENSE' is not a recognised SPDX identifier |
| 04.flags_accumulating | few or no feature flags in the history |
| 04.api_versions_coexisting | one API version is served, or none |
| 04.releases_stopped | too few tagged releases to judge a cadence |
| 04.release_branch | too few release tags to tell |
| 05.project_advisories | record incomplete: no advisory found in the sources that answered; NVD: 32 records name storefront with nothing tying them to this repository (CVE-2003-0557, CVE-2005-0935, CVE-2005-0936, …) |
| 05.advisory_record | record incomplete: no advisory against the project in the last 24 months; NVD: 32 records name storefront with nothing tying them to this repository (CVE-2003-0557, CVE-2005-0935, CVE-2005-0936, …) |
| 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 FDSM-99YB-7YVM 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/FDSM99YB7YVM?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: 25.5authenticated: False |
| 4.6s | cloned the repository to a temporary directory | depth: full |
| 11.1s | read the git history | commits: 972tracked files: 1099 |
| 86.5s | ran the deterministic checks | blame pass: Trueread working tree: False |
| 86.5s | recorded where this scan ran | attested: Falseenvironment: cloud-run |
| 120.0s | kept the facts, never the source, for re-reading under new checks | |
| 120.0s | deleting the working copy |
Total 120.0s ·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).