18d55eb · 11,175 commits · 2,960 files
Issued 2026-09-29
Nothing significant. Questions worth asking about Organization & Key-Person Risk, Security & Reliability Posture.
105 checks ran across 6 assessable dimensions. None found a significant problem; 4 raised something worth a question. 9 findings, each with evidence. One dimension cannot be assessed without an acquirer.
- 05.60 Relicensed: GPL-2.0 → GPL-3.0 (2013-04-12) COPYING
- 1 submodule(s) this survey does not read: fastlane .gitmodules:1
- Words about people are today's: bands rather than exact shares, dates or day counts, and what the history measured rather than why.
- 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 | adequate | |
| 02 | Engineering Process & SDLC Maturity | strong | |
| 03 | Organization & Key-Person Risk | adequate | |
| 04 | Product & Engineering Maturity | adequate | |
| 05 | Security & Reliability Posture | adequate | |
| 06 | Observability & Operations | not assessable | |
| 07 | Fit with the Acquirer | not assessable |
- 25% of non-merge commits carry any trailer at all
- low trailer coverage: the convention may not be in consistent use
- 33% of commits show author/committer date divergence, which is the shape of replayed history that can drop trailers
Architecture & Codebase — including AI provenance
01 · adequate · ratings ↑app/src/full/java/vendored/org/apache/commons/codec/digest/DigestUtils.java is 1,744 lines, 18× this codebase's median file
adequateThe median source file here is 93 lines. 3 files exceed 1,000 lines, the largest being 1,744. 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.
| line-count | app/src/full/java/vendored/org/apache/commons/codec/digest/DigestUtils.java:1 — 1,744 lines (18× median) |
| line-count | app/src/full/java/org/fdroid/fdroid/nearby/SwapWorkflowActivity.java:1 — 1,626 lines (17× median) |
| line-count | libs/database/src/main/java/org/fdroid/database/AppDao.kt:1 — 1,020 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 · adequate · ratings ↑Bus factor 1: recent work is concentrated in one contributor
adequateIn the last 24 months, one contributor authored more than half of 1,351 non-merge commits among 240 authors; across all history, less than a quarter of 9,655. In a project with 240 recent contributors and 16 years of history, that is a question about one person's role rather than a fragile team — but it is the question to ask.
| git shortlog -sn | last 24 months: top author more than half of 1,351 commits; bus factor 1; 240 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.
The bus factor fell from 19 to 1
adequateYear by year, newest first, the number of people who wrote half the changes was 1, 19, 14, 8. The team narrowed to one person, which is a different risk from one that always was: the code does not say why.
| bus factor by year | 1, 19, 14, 8 |
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.
Regular contributors fell from 50 to 11 in a year
adequate42 people who committed regularly the year before made no commits in the last year, and 5 new regular contributors arrived. Ask whether the work they did is still covered.
| regular contributors by year | 50 then 11; 42 stopped committing, 5 began |
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 · adequate · ratings ↑19% of bug fixes add or change a test
adequateOf 129 fixes in the last 24 months, 24 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 | 24 of 129 |
Respond to this finding
Your response is published beside the finding, not instead of it. A finding you can argue with is the point — and a wrong one is calibration data we want.
An owner's response is removed only when it is unlawful, impersonates someone, publishes personal data or a credential, or is not about the finding. Disagreeing with the report is never a reason. To report a response, or to reach us about one, write to takedown@borehole.dev.
6 files still carry code deprecated more than two years ago
adequate6 files were marked deprecated over two years ago and still are, the oldest since Nov 2022. A deprecation is a promise to remove. Ask what still depends on these, and whether removing them is scheduled.
| libs/download/src/androidMain/kotlin/org/fdroid/download/HttpDownloader.kt | libs/download/src/androidMain/kotlin/org/fdroid/download/HttpDownloader.kt — deprecated since Nov 2022 |
| libs/download/src/androidMain/kotlin/org/fdroid/download/HttpDownloaderV2.kt | libs/download/src/androidMain/kotlin/org/fdroid/download/HttpDownloaderV2.kt — deprecated since Dec 2022 |
| libs/download/src/commonMain/kotlin/org/fdroid/download/DownloadRequest.kt | libs/download/src/commonMain/kotlin/org/fdroid/download/DownloadRequest.kt — deprecated since Dec 2022 |
| libs/index/src/androidMain/kotlin/org/fdroid/index/IndexUtils.kt | libs/index/src/androidMain/kotlin/org/fdroid/index/IndexUtils.kt — deprecated since Jan 2023 |
| libs/database/src/main/java/org/fdroid/database/RepositoryDao.kt | libs/database/src/main/java/org/fdroid/database/RepositoryDao.kt — deprecated since Aug 2023 |
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 ↑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 2,960 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.
The app allows plain HTTP to any server
adequateThe app's manifest allows unencrypted HTTP app-wide (NSAllowsArbitraryLoads, or cleartext traffic permitted), rather than for named domains. Anything sent over plain HTTP can be read on the network, and enterprise security reviews ask about it. Some apps need it by nature (a podcast or feed reader fetches whatever URL a feed gives), so ask which case this is.
| app/src/full/AndroidManifest.xml | app/src/full/AndroidManifest.xml:46 — cleartext allowed app-wide |
| app/src/full/res/xml/network_security_config.xml | app/src/full/res/xml/network_security_config.xml:3 — cleartext allowed app-wide |
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: GPL-2.0 → GPL-3.0 (2013-04-12)
adequateThe root licence changed 1 time(s). Code taken under earlier terms stays under them; check which terms any fork or customer relied on.
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 · not assessable · ratings ↑Not rated: only 5 of 16 checks could reach a conclusion here; the rest do not apply to this repository or could not read it. What a person adds here.
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
2 checks against the running system follow from the findings above: what a buyer's engineer will try, how to run it first, and what to have ready. A paid survey of this repository includes them.
A paid survey of a public repository is also reviewed: a language model reads each finding against the code and withdraws only findings it judges the code contradicts, each listed with its reason. The review is a language model's reading of the findings against the code, and it can be wrong. It never adds a finding, never raises a band, and never removes a finding from a proven check or an advisory that affects the surveyed version.
What a person adds
The survey reads what the repository can show. The code cannot settle these questions, and on them this report states nothing. Each says where its answer lives: your own engineer, the company, or an assessor you choose can settle it. Questions marked measured open with something this repository shows.
Architecture & Codebase — including AI provenance
01 · full coverage- measured No architecture or design document is in the tree, across 2,770 product files. Where does the design live, and who holds it?
- measured The repository pulls code in through git submodules (.gitmodules). A buyer receives pointers, not that code. Can every submodule be fetched without the team's credentials, and who owns each one?
- 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 951 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- 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 The Android app requests 2 sensitive permissions: MANAGE_EXTERNAL_STORAGE, QUERY_ALL_PACKAGES. Does the product need each one, and has the store's review accepted them?
- 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 coverageNot rated: only 5 of 16 checks could reach a conclusion here; the rest do not apply to this repository or could not read it.
- 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 Kotlin codebase, with Java alongside (22% of source files). Does your engineering organisation already run Kotlin in production, or would this be the first?
- The bulk of this system sits in app/, libs/, src/. Which of your existing systems would each of those have to absorb or replace?
- Nothing in the repository says how this is deployed. Is it shipped as a library, a binary or a service, and if it runs somewhere, who owns that environment?
- 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/gitlab.com/fdroid+fdroidclient/18d55eb)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 — 96 signals that ran and did not fire
Appendix: rejection log — 96 signals that ran and did not fire
Published on purpose. A signal that looked and decided not to fire has told you something, and this is the calibration data behind every threshold above.
Looked, and found nothing — 62
| Signal | What it found |
|---|---|
| 04.hotspot_concentration | change is spread across the codebase rather than pooling in a few filesfiles 14,320 · top5 share 0.027 |
| 04.debt_markers | debt markers are sparsemarkers 51 · per kloc 0.4 · lines read 128,547 |
| 04.test_growth | test effort kept pace with code writtenlate test per code 0.399 · early test per code 0.036 |
| 04.churn_trend | rework is not rising against new worklate delete per insert 0.634 · early delete per insert 0.391 |
| 04.fix_share_trend | fixing is not crowding out building |
| 04.compat_layers | little code is kept for the old wayshare 0.002 · code files 410 · compat files 1 |
| 06.telemetry_presence | this repository does not deploy a running service, so instrumentation is not expected of itbasis nothing in this repository deploys a long-running server; if it runs as one, its deployment lives elsewhere · files read 2,622 |
| 06.structured_logging | not a running service; structured logging is not expected of a librarybasis nothing in this repository deploys a long-running server; if it runs as one, its deployment lives elsewhere |
| 06.healthcheck_presence | not a running service, so a health endpoint is not expectedbasis nothing in this repository deploys a long-running server; if it runs as one, its deployment lives elsewhere |
| 06.usage_reporting_default | the product's code names no reporting hostsettings on 0 · settings off 0 |
| 06.migrate_on_start | migrations do not run at container start |
| 03.active_contributors | more than one contributor active in the trailing yearall time 951 · active 12mo 31 |
| 03.knowledge_silos | every substantial directory has been touched by more than one personauthors 951 · directories 4 |
| 03.drive_by_contributors | an open contributor base, where one-commit contributors are normalauthors 951 · one off share 0.611 |
| 03.contributor_attrition | no contributor dominates enough for their absence to matterauthors 951 · 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 240 |
| 03.second_contributor_attrition | the second and third contributors are still active |
| 02.merge_discipline | a meaningful share of recent change carries evidence of reviewmerges 275 · window last 24 months · with tracked 81 |
| 02.ci_presence | CI configuration is present in the working treecount 1 |
| 02.test_presence | tests are present in a normal proportion to sourcetests 120 · source 530 · test ratio 0.226 |
| 02.release_cadence | tags are presenttags 331 |
| 02.conventional_commits | commit subjects generally carry contentsampled 9,655 · low content share 0.007 |
| 02.branch_protection_hints | process scaffolding is present in the repository |
| 02.ci_runs_tests | CI invokes a test runnerconfigs 1 · with tests 1 |
| 02.skipped_tests | few tests are switched offfocused 0 · skipped 6 · test files 171 |
| 02.ci_test_gating | no test run in CI is written so that it cannot failconfigs 1 |
| 02.revert_share | change is rarely undoneshare 0.004 · reverts 5 · recent commits 1,351 |
| 02.flaky_test_markers | tests are not retried until they passtest retries 0 · suite retries 0 |
| 02.long_lived_branches | the typical branch reaches the trunk quicklyshare 0.062 · merges 209 · long lived 13 |
| 02.commit_size | changes arrive in reviewable sizesshare 0.007 · commits 1,244 · over 2000 lines 9 |
| 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 2,373 · share of insertions 0.002 |
| 01.message_uniformity | commit subjects vary in wording and lengthlength stdev 26.94 · repeat share 0.241 |
| 01.revision_depth | most files were revisited after they were first writtenfiles seen 2,482 · write once share 0.572 |
| 01.duplicated_blocks | little shipping code is repeated verbatim across filesshare 0.0046 · product files 410 · distinct blocks 36,759 |
| 01.swallowed_errors | errors are rarely thrown awayloc 131,151 · files 4 · per kloc 0.04 |
| 01.unfinished_migration | Java to Kotlin: the move is still under way: the new language's share rose in the last yearmigration Java to Kotlin · new share now 0.678 · new share at start 0.005 |
| 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 2,622 |
| 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,078,187 |
| 05.secrets_management_pattern | no environment file is committed outside tests and examplesenv files 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.known_vulnerabilities | no locked dependency has a published advisoryadvisories 0 · dependencies 74 · high or critical 0 |
| 05.privileged_workloads | no workload runs privileged or in the host's namespacessites 0 · behind a setting or built here 0 |
| 05.credentials_in_deploy_config | deployment configuration references secrets, never holds themfiles 0 · sites 0 |
| 05.signing_material | no signing keystore or profile is committedfiles 0 |
| 05.license_copyleft_inherited | every licence found in vendored code is permissive or weak-copyleftvendored paths 12 |
| 05.license_vendored_unlicensed | all 1 vendored components state their terms, in a licence file, their own headers or a notices filecomponents 1 · stated in headers or notices 1 |
| 05.license_grant_unclear | the licence is recognisable as GPL-3.0class strong-copyleft · license GPL-3.0 |
| 05.committed_native_libraries | no widely used compiled library is committed to the productlibraries 0 |
| 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 14.5 · days since last tag -1 · commits last 90 days 175 |
| 04.release_branch | the newest release was cut from the branch surveyedelsewhere 77 · on branch 254 · tags in window 331 |
| 03.single_maintainer | no file says one person maintains itstatements 0 |
| 05.project_advisories | no published advisory affects the surveyed versionaffecting 0 · exploited 0 · advisories 0 |
| 05.advisory_record | no advisory against the project in the last 24 monthscritical 0 · affecting 0 · could not tell 0 |
| 05.project_exploited | no affecting advisory is on CISA's Known Exploited listexploited 0 |
Could not conclude, or did not apply — 34
Not a clean result. Each says why it could not answer here.
| Signal | Why |
|---|---|
| 04.dependency_sprawl | no recognised dependency manifest found |
| 04.eol_runtime | no pinned runtime version to check |
| 04.schema_churn | no schema migrations to read |
| 04.dependency_redundancy | no JavaScript manifest to read |
| 06.telemetry_depth | not expected of it: nothing in this repository deploys a long-running server; if it runs as one, its deployment lives elsewhere |
| 06.print_logging | not expected of it: nothing in this repository deploys a long-running server; if it runs as one, its deployment lives elsewhere |
| 06.correlation_ids | not expected of it: nothing in this repository deploys a long-running server; if it runs as one, its deployment lives elsewhere |
| 06.error_reporting | not expected of it: nothing in this repository deploys a long-running server; if it runs as one, its deployment lives elsewhere |
| 06.alert_rules | not expected of it: nothing in this repository deploys a long-running server; if it runs as one, its deployment lives elsewhere |
| 06.deployed_image_floats | not expected of it: nothing in this repository deploys a long-running server; if it runs as one, its deployment lives elsewhere |
| 06.probes_identical | no Kubernetes probes |
| 06.single_replica | no Kubernetes deployments |
| 06.environment_branching | not expected of it: nothing in this repository deploys a long-running server; if it runs as one, its deployment lives elsewhere |
| 06.release_markers | not expected of it: nothing in this repository deploys a long-running server; if it runs as one, its deployment lives elsewhere |
| 06.feature_flags | no feature-flag service; flags may live elsewhere |
| 02.dependency_update_cadence | no lockfile to date |
| 01.build_reproducibility | no product Dockerfile to read |
| 01.notebook_outputs | not a data or machine-learning repository |
| 05.dependency_pinning | no manifest whose pinning can be read without a lockfile |
| 05.container_runs_as_root | no Dockerfile to read |
| 05.supply_chain_pinning | no CI actions or pipe-to-shell installs to check |
| 05.outbound_timeouts | not a running service |
| 05.migration_reversibility | too few migrations to judge |
| 05.sql_from_strings | not a running service; a library that builds SQL is doing its job |
| 05.resource_limits | no Kubernetes workload manifests |
| 05.public_env_secret | not a frontend |
| 05.unsafe_html | not a frontend |
| 05.source_maps_shipped | not a frontend |
| 05.dataset_provenance | not a data or machine-learning repository |
| 05.license_manifest_conflict | no packaging manifest states a licence |
| 04.flags_accumulating | few or no feature flags in the history |
| 04.api_versions_coexisting | not a running service |
| 04.dependency_churn | few dependencies were added and dropped within 60 days |
| 04.ci_platforms_dropped | no platform was dropped from CI in the last two years |
Anyone can check this report against the authoritative record — click the stamp, or enter 37FE-CSJW-8SCF 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/37FECSJW8SCF?via=badge)
A survey is a reading by a particular version of the assessor. Older readings are kept rather than replaced, because a verification mark attests to the survey it was issued for — overwriting one would make every code already in circulation read as tampered.
| Read | Assessor | Findings | Band |
|---|---|---|---|
| 2026-09-29 · shown | borehole 0.7.6 | 10 | adequate |
9 other readings (show)
| 2026-10-04 | borehole 0.7.13 | 10 | adequate |
| 2026-10-03 | borehole 0.7.12 | 10 | adequate |
| 2026-10-03 | borehole 0.7.11 | 10 | adequate |
| 2026-10-02 | borehole 0.7.10 | 10 | adequate |
| 2026-10-01 | borehole 0.7.9 | 10 | adequate |
| 2026-09-30 | borehole 0.7.8 | 10 | adequate |
| 2026-09-28 | borehole 0.7.5 | 10 | adequate |
| 2026-09-28 | borehole 0.7.4 | 10 | adequate |
| 2026-09-27 | borehole 0.7.3 | 10 | adequate |
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 GitLab API | authenticated: False |
| 7.0s | cloned the repository to a temporary directory | depth: full |
| 13.6s | read the git history | commits: 11175tracked files: 2960 |
| 80.0s | ran the deterministic checks | blame pass: Falseread working tree: False |
| 80.0s | recorded where this scan ran | attested: Falseenvironment: cloud-run |
| 106.6s | kept the facts, never the source, for re-reading under new checks | |
| 106.6s | deleting the working copy |
Total 106.6s ·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).