1065a71 · 50,000 commits · 7,816 files
Issued 2026-10-22
Reads strong: 5 of 6 rated dimensions are strong, 1 is adequate and none is significant.
104 checks ran across 6 assessable dimensions. Observability & Operations is adequate. 6 findings, each with evidence. One dimension cannot be assessed without an acquirer.
This repository reads strong. Show it in your README: the badge links to a page where anyone can check the reading. If you embed it: link it to the report, remove it if the report is delisted, and do not present it as a certification or an endorsement.
[](https://borehole.dev/verify/T2SS31BP5ZKA?via=badge)- names Apache Software Foundation README.md:99
- 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 | strong | |
| 03 | Organization & Key-Person Risk | strong | |
| 04 | Product & Engineering Maturity | strong | |
| 05 | Security & Reliability Posture | strong | |
| 06 | Observability & Operations | adequate | |
| 07 | Fit with the Acquirer | not assessable |
- 3% of non-merge commits carry any trailer at all
- low trailer coverage: the convention may not be in consistent use
- 21% of commits show author/committer date divergence, which is the shape of replayed history that can drop trailers
Architecture & Codebase — including AI provenance
01 · strong · ratings ↑apps/files/js/filelist.js is 3,462 lines, 43× this codebase's median file
adequateThe median source file here is 80 lines. 32 files exceed 1,000 lines, the largest being 3,462. 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 | apps/files/js/filelist.js:1 — 3,462 lines (43× median) |
| line-count | core/js/js.js:1 — 3,238 lines (40× median) |
| line-count | lib/private/Share/Share.php:1 — 3,124 lines (39× median) |
| line-count | .drone.star:1 — 2,730 lines (34× median) |
| line-count | lib/private/Files/View.php:1 — 2,290 lines (28× median) |
Respond to this finding
Your response is published beside the finding, not instead of it. A finding you can argue with is the point — and a wrong one is calibration data we want.
An owner's response is removed only when it is unlawful, impersonates someone, publishes personal data or a credential, or is not about the finding. Disagreeing with the report is never a reason. To report a response, or to reach us about one, write to takedown@borehole.dev.
Engineering Process & SDLC Maturity
02 · strong · ratings ↑No finding. 16 checks ran and none fired; the rejection log below says why each did not.
Organization & Key-Person Risk
03 · strong · ratings ↑No finding. 10 checks ran and none fired; the rejection log below says why each did not.
Product & Engineering Maturity
04 · strong · ratings ↑No finding. 19 checks ran and none fired; the rejection log below says why each did not.
Security & Reliability Posture
05 · strong · ratings ↑The build runs third-party code it does not pin
adequate4 third-party CI actions are referenced by a tag or branch rather than a commit, so they run whatever that tag points to on the day. 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/changelog.yml | .github/workflows/changelog.yml:13 — action pinned by tag |
| .github/workflows/ci.yml | .github/workflows/ci.yml:23 — action pinned by tag |
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 deserialisers that can run code
adequate6 places read data with a deserialiser that executes what it reads (PHP `unserialize`). 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.
| apps/dav/lib/DAV/AbstractCustomPropertiesBackend.php | apps/dav/lib/DAV/AbstractCustomPropertiesBackend.php:315 — code-executing deserialiser |
| lib/private/Command/CallableJob.php | lib/private/Command/CallableJob.php:28 — code-executing deserialiser |
| lib/private/Command/ClosureJob.php | lib/private/Command/ClosureJob.php:28 — 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.
1 locked dependency has published vulnerabilities
adequate1 of 68 locked dependencies match 1 published advisories in OSV. A lockfile says which version is installed, not whether the flawed code is reachable from this product, so each needs a look. Most are fixed by an upgrade, and the advisory names the version.
A note that does not affect this rating: in Borehole's calibration, this check's notes were usually true but overstated.
| composer.lock | composer.lock — league/flysystem 1.1.10: GHSA-cxf4-7mrp-vvpr (low), fixed in 3.35.3 |
Respond to this finding
Your response is published beside the finding, not instead of it. A finding you can argue with is the point — and a wrong one is calibration data we want.
An owner's response is removed only when it is unlawful, impersonates someone, publishes personal data or a credential, or is not about the finding. Disagreeing with the report is never a reason. To report a response, or to reach us about one, write to takedown@borehole.dev.
1 vendored component with no licence
adequateThird-party code is committed into this repository without any statement of the terms it arrived under. Unknown terms are harder to deal with than inconvenient ones: an awkward licence can be complied with, an absent one cannot. Each of these needs its origin established before the code changes hands.
A note that does not affect this rating: in Borehole's calibration, this check's notes were usually true but overstated.
| apps/federatedfilesharing/css/3rdparty/gs-share | apps/federatedfilesharing/css/3rdparty/gs-share — 1 tracked files, no licence file |
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 ↑Sends usage data to telemetry.owncloud.com by default
adequateconfig/config.sample.php sends to telemetry.owncloud.com, and config/config.sample.php leaves reporting on as shipped. Every installation reports to the vendor unless its operator turns this off. For a buyer running it inside their own product, that is an outbound data flow to a third party: ask what is sent, how often, and whether the buyer's customers were told.
| config/config.sample.php | config/config.sample.php:1890 — reports to telemetry.owncloud.com |
| config/config.sample.php | config/config.sample.php:1896 — the reporting setting is on by default |
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
4 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 (DESIGN.md). Does it match what the team believes today? Ask them to walk through it against the code.
- Is the architecture right for the next three years of the product?
- Were the home-grown components reasonable choices when they were made, and are they now?
Engineering Process & SDLC Maturity
02 · high coverage- Is review real or a rubber stamp? Comment depth and time to approve need the pull request history.
- Is delivery planned and measured, or heroic?
- How are incidents run, reviewed and learned from?
Organization & Key-Person Risk
03 · partial coverage- measured 606 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 217 commits landed in the last year, against 85 the year before (+155%). 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- 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- 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 PHP codebase, with JavaScript alongside (48% of source files). Does your engineering organisation already run PHP in production, or would this be the first?
- The bulk of this system sits in apps/, l10n/, lib/. 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/owncloud/core/1065a71)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 — 98 signals that ran and did not fire
Appendix: rejection log — 98 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 — 55
| Signal | What it found |
|---|---|
| 04.hotspot_concentration | change is spread across the codebase rather than pooling in a few files, in the most recent 50,000 commits (3 Jul 2011 to 22 Oct 2026)files 65,128 · top5 share 0.012 · history read the most recent 50,000 commits (3 Jul 2011 to 22 Oct 2026) |
| 04.debt_markers | debt markers are sparsemarkers 489 · per kloc 0.58 · lines read 847,143 |
| 04.churn_trend | rework is not rising against new work, in the most recent 50,000 commits (3 Jul 2011 to 22 Oct 2026)history read the most recent 50,000 commits (3 Jul 2011 to 22 Oct 2026) · late delete per insert 0.509 · early delete per insert 0.91 |
| 04.fixes_with_tests | fixes usually come with a testfixes 92 · share 0.598 · with tests 55 |
| 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 6,412 |
| 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.migrate_on_start | migrations do not run at container start |
| 03.contributor_concentration | no single contributor dominates the last 24 monthswindow last 24 months · authors 606 · top share a quarter or more |
| 03.critical_path_ownership | more than one person changes the critical pathsauthors 12 |
| 03.second_contributor_attrition | the second and third contributors are still active |
| 03.bus_factor_trend | the team has not narrowed to one person |
| 02.merge_discipline | a meaningful share of recent change carries evidence of reviewmerges 39 · window last 24 months · with tracked 13 |
| 02.ci_presence | CI configuration is present in the working treecount 11 |
| 02.test_presence | tests are present in a normal proportion to sourcetests 1,718 · source 4,755 · test ratio 0.361 |
| 02.conventional_commits | commit subjects generally carry content, in the most recent 50,000 commits (3 Jul 2011 to 22 Oct 2026)sampled 36,035 · history read the most recent 50,000 commits (3 Jul 2011 to 22 Oct 2026) · low content share 0.017 |
| 02.branch_protection_hints | process scaffolding is present in the repository |
| 02.ci_runs_tests | CI invokes a test runnerconfigs 11 · with tests 4 |
| 02.skipped_tests | few tests are switched offfocused 0 · skipped 1 · test files 2,171 |
| 02.ci_test_gating | no test run in CI is written so that it cannot failconfigs 11 |
| 02.revert_share | change is rarely undoneshare 0.0 · reverts 0 · recent commits 302 |
| 02.dependency_update_cadence | dependencies move with the codelockfiles 2 · commits since 1 · days since lockfile changed 1 |
| 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 2 · ci configs 11 · product files 3,045 |
| 02.long_lived_branches | the typical branch reaches the trunk quicklyshare 0.026 · merges 39 · long lived 1 |
| 02.commit_size | changes arrive in reviewable sizesshare 0.031 · commits 262 · over 2000 lines 8 |
| 01.burst_import | no commit run met both the rate and the net-addition threshold, in the most recent 50,000 commits (3 Jul 2011 to 22 Oct 2026)gap seconds 180 · history read the most recent 50,000 commits (3 Jul 2011 to 22 Oct 2026) · min add ratio 3.0 |
| 01.message_uniformity | commit subjects vary in wording and length, in the most recent 50,000 commits (3 Jul 2011 to 22 Oct 2026)history read the most recent 50,000 commits (3 Jul 2011 to 22 Oct 2026) · length stdev 26.84 · repeat share 0.159 |
| 01.duplicated_blocks | little shipping code is repeated verbatim across filesshare 0.026 · product files 3,037 · distinct blocks 198,784 |
| 01.swallowed_errors | errors are rarely thrown awayloc 851,966 · files 8 · per kloc 0.01 |
| 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 6,412 |
| 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.shell_from_strings | product code does not build shell commands from stringssites 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.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 77 |
| 05.license_manifest_conflict | manifest and licence file agree on AGPL-3.0license AGPL-3.0 |
| 05.license_grant_unclear | the licence is recognisable as AGPL-3.0class network-copyleft · license AGPL-3.0 |
| 05.committed_native_libraries | no widely used compiled library is committed to the productlibraries 0 |
| 04.dependency_churn | few dependencies were added and dropped within 60 daysdependencies seen 139 · added in two years 3 · removed within 60 days 0 |
| 04.ci_platforms_dropped | no platform was dropped from CI in the last two years |
| 04.repository_status | the README's first screen states no end, move or freezestatements 0 |
| 02.development_elsewhere | nothing says development happens elsewhereno pr statements 0 · mirror statements 0 · replayed commit share 0.0 |
| 05.licence_changes | the root licence has not changed in the history readlicence versions 1 · unreleased changes 0 |
| 05.paid_edition | no directory carries a separate paid-edition licencedirectories 0 |
| 04.releases_stopped | releases keep pace with developmentmedian gap days 5.0 · days since last tag 16 · commits last 90 days 113 |
| 04.release_branch | the newest release was cut from the branch surveyed, in the most recent 50,000 commits (3 Jul 2011 to 22 Oct 2026)elsewhere 375 · on branch 154 · history read the most recent 50,000 commits (3 Jul 2011 to 22 Oct 2026) |
| 03.single_maintainer | no file says one person maintains itstatements 0 |
Could not conclude, or did not apply — 43
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.fix_share_trend | fewer than six busy quarters to compare |
| 04.schema_churn | no schema migrations to read |
| 04.compat_layers | a library, whose compatibility code is usually deliberate |
| 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 |
| 03.active_contributors | not assessed: this check needs the whole history, and only the most recent 50,000 commits (3 Jul 2011 to 22 Oct 2026) were read |
| 03.knowledge_silos | not assessed: this check needs the whole history, and only the most recent 50,000 commits (3 Jul 2011 to 22 Oct 2026) were read |
| 03.drive_by_contributors | not assessed: this check needs the whole history, and only the most recent 50,000 commits (3 Jul 2011 to 22 Oct 2026) were read |
| 03.contributor_attrition | not assessed: this check needs the whole history, and only the most recent 50,000 commits (3 Jul 2011 to 22 Oct 2026) were read |
| 03.joiners_and_leavers | too few regular contributors to see a trend |
| 02.release_cadence | not assessed: this check needs the whole history, and only the most recent 50,000 commits (3 Jul 2011 to 22 Oct 2026) were read |
| 01.initial_dump | not assessed: this check needs the whole history, and only the most recent 50,000 commits (3 Jul 2011 to 22 Oct 2026) were read |
| 01.revision_depth | not assessed: this check needs the whole history, and only the most recent 50,000 commits (3 Jul 2011 to 22 Oct 2026) were read |
| 01.build_reproducibility | no product Dockerfile to read |
| 01.notebook_outputs | not a data or machine-learning repository |
| 05.container_runs_as_root | no Dockerfile to read |
| 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.cleartext_traffic | not a mobile app |
| 05.dataset_provenance | not a data or machine-learning repository |
| 04.flags_accumulating | few or no feature flags in the history |
| 04.api_versions_coexisting | not a running service |
| 04.deprecations_lingering | a library, which keeps deprecated interfaces for its users |
| 05.project_advisories | record incomplete: no advisory found in the sources that answered; NVD did not |
| 05.advisory_record | record incomplete: no advisory against the project in the last 24 months; NVD did not answer |
| 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 T2SS-31BP-5ZKA 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/T2SS31BP5ZKA?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: 349.8authenticated: False |
| 64.9s | cloned the repository to a temporary directory | depth: full |
| 130.7s | read the git history | commits: 50000tracked files: 7816 |
| 471.7s | ran the deterministic checks | blame pass: Falseread working tree: False |
| 471.8s | recorded where this scan ran | attested: Falseenvironment: cloud-run |
| 680.4s | kept the facts, never the source, for re-reading under new checks | |
| 680.4s | deleting the working copy |
Total 680.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).