6b03c5e · 6,812 commits · 3,547 files
Issued 2026-11-07
Nothing significant. Questions worth asking about Organization & Key-Person Risk.
105 checks ran across 6 assessable dimensions. None found a significant problem; 1 raised something worth a question. 7 findings, each with evidence. One dimension cannot be assessed without an acquirer.
- 05.60 Relicensed: LGPL-3.0 → MIT (2019-11-17) license.txt
- 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 | strong | |
| 03 | Organization & Key-Person Risk | adequate | |
| 04 | Product & Engineering Maturity | strong | |
| 05 | Security & Reliability Posture | strong | |
| 06 | Observability & Operations | not assessable | |
| 07 | Fit with the Acquirer | not assessable |
- 12% 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
Architecture & Codebase — including AI provenance
01 · strong · ratings ↑src/PhpSpreadsheet/Reader/Xls.php is 4,923 lines, 74× this codebase's median file
adequateThe median source file here is 66 lines. 20 files exceed 1,000 lines, the largest being 4,923. 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 | src/PhpSpreadsheet/Reader/Xls.php:1 — 4,923 lines (74× median) |
| line-count | src/PhpSpreadsheet/Worksheet/Worksheet.php:1 — 4,337 lines (65× median) |
| line-count | src/PhpSpreadsheet/Writer/Xls/Worksheet.php:1 — 3,262 lines (49× median) |
| line-count | src/PhpSpreadsheet/Reader/Xlsx.php:1 — 3,132 lines (47× median) |
| line-count | src/PhpSpreadsheet/Calculation/Calculation.php:1 — 3,088 lines (46× 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,105 non-merge commits among 51 authors; across all history, a quarter or more of 5,129. In a project with 51 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,105 commits; bus factor 1; 51 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 contributor who wrote a quarter or more of this has not committed here for more than two years
adequateOne person authored a quarter or more of 5,129 commits and has not committed here for more than two years, while the repository has kept moving. The concentration figure alone would not show this. Whoever is changing this code now is not the person who wrote most of it, which is the situation an acquirer is usually told they are avoiding. The history shows only that no commits of theirs landed here, not why.
| last-commit-by-top-author | last commit more than two years ago, measured to the survey |
| git shortlog -sn | top author a quarter or more of 5,129 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.
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/github-pages.yml | .github/workflows/github-pages.yml:19 — action pinned by tag |
| .github/workflows/github-pages.yml | .github/workflows/github-pages.yml:30 — 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.
2 deserialisers that can run code
adequate2 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.
| src/PhpSpreadsheet/Spreadsheet.php | src/PhpSpreadsheet/Spreadsheet.php:1160 — code-executing deserialiser |
| src/PhpSpreadsheet/Worksheet/Worksheet.php | src/PhpSpreadsheet/Worksheet/Worksheet.php:4058 — 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: LGPL-3.0 → MIT (2019-11-17)
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".
| 509f27e5c | license.txt — LGPL-3.0 from 2010-08-26 |
| 86bb4f935 | LICENSE — MIT from 2019-11-17 |
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.
25 advisories against this project in the last 24 months, 17 high or critical
adequateThe newest was published on 2026-10-12. A project that publishes advisories is telling its users about its fixes, and the count and pace say how much security work it carries. None of them affects the surveyed version. The record is incomplete: NVD: 2 records name PhpSpreadsheet with nothing tying them to this repository (CVE-2025-58051, CVE-2026-86020).
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-rxj4-h86g-25gc | 2026-10-12: GHSA-rxj4-h86g-25gc (high), fixed in 3.10.8: XmlScanner Bypass via Double-Encoded unentity() TOCTOU Allows XXE and Denial of Service |
| GHSA-3x94-m842-937c | 2026-10-12: GHSA-3x94-m842-937c (high), fixed in 1.30.7: XmlScanner Bypass via ISO-2022 Escape Sequences Allows XXE and Denial of Service |
| GHSA-j2w7-387v-m2rq | 2026-10-12: GHSA-j2w7-387v-m2rq (high), fixed in 1.30.7: ODS Reader: Unbounded number-rows-repeated → CPU & Memory Exhaustion (DoS) |
| GHSA-2phh-27fw-q4gc | 2026-10-12: GHSA-2phh-27fw-q4gc (moderate), fixed in 1.30.7: SSRF whitelist bypass via unre-validated HTTP redirect in Drawing::setPath external image loading |
| GHSA-xh5m-36r6-47m3 | 2026-07-19: GHSA-xh5m-36r6-47m3 (high), fixed in 1.30.6: XLS/OLE sector-chain self-loop causes memory exhaustion |
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
1 check 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/topics/architecture.md). Does it match what the team believes today? Ask them to walk through it against the code.
- Is the architecture right for the next three years of the product?
- Were the home-grown components reasonable choices when they were made, and are they now?
Engineering Process & SDLC Maturity
02 · high coverage- Is review real or a rubber stamp? Comment depth and time to approve need the pull request history.
- Is delivery planned and measured, or heroic?
- How are incidents run, reviewed and learned from?
Organization & Key-Person Risk
03 · partial coverage- measured 424 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 05.5 found credential-shaped strings in this repository. Was each one revoked at the provider? Deleting it from the code revokes nothing; only the provider's audit log shows that it was.
- 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 PHP codebase. Does your engineering organisation already run PHP in production, or would this be the first?
- The bulk of this system sits in src/, infra/, bin/. 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/phpoffice/phpspreadsheet/6b03c5e)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 — 63
| Signal | What it found |
|---|---|
| 04.hotspot_concentration | change is spread across the codebase rather than pooling in a few filesfiles 8,103 · top5 share 0.033 |
| 04.debt_markers | debt markers are sparsemarkers 53 · per kloc 0.16 · lines read 336,211 |
| 04.test_growth | test effort kept pace with code writtenlate test per code 1.017 · early test per code 0.108 |
| 04.churn_trend | rework is not rising against new worklate delete per insert 0.707 · early delete per insert 0.518 |
| 04.fixes_with_tests | fixes usually come with a testfixes 94 · share 0.691 · with tests 65 |
| 04.fix_share_trend | fixing is not crowding out building |
| 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,750 |
| 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 424 · active 12mo 34 |
| 03.knowledge_silos | every substantial directory has been touched by more than one personauthors 424 · directories 5 |
| 03.drive_by_contributors | an open contributor base, where one-commit contributors are normalauthors 424 · one off share 0.672 |
| 03.critical_path_ownership | more than one person changes the critical pathsauthors 51 |
| 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 5 · joined 16 · regular last year 18 |
| 02.merge_discipline | a meaningful share of recent change carries evidence of reviewmerges 663 · window last 24 months · with tracked 134 |
| 02.ci_presence | CI configuration is present in the working treecount 2 |
| 02.test_presence | tests are present in a normal proportion to sourcetests 1,772 · source 2,329 · test ratio 0.761 |
| 02.release_cadence | tags are presenttags 147 |
| 02.conventional_commits | commit subjects generally carry contentsampled 5,278 · 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 2 · with tests 1 |
| 02.skipped_tests | few tests are switched offfocused 0 · skipped 0 · test files 2,211 |
| 02.ci_test_gating | no test run in CI is written so that it cannot failconfigs 2 |
| 02.revert_share | change is rarely undoneshare 0.0 · reverts 0 · recent commits 1,105 |
| 02.dependency_update_cadence | dependencies move with the codelockfiles 1 · commits since 15 · days since lockfile changed 4 |
| 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 1 · ci configs 2 · product files 557 |
| 02.long_lived_branches | the typical branch reaches the trunk quicklyshare 0.036 · merges 471 · long lived 17 |
| 02.commit_size | changes arrive in reviewable sizesshare 0.005 · commits 1,029 · over 2000 lines 5 |
| 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 234,454 · share of insertions 0.1959 |
| 01.message_uniformity | commit subjects vary in wording and lengthlength stdev 42.35 · repeat share 0.171 |
| 01.revision_depth | most files were revisited after they were first writtenfiles seen 624 · write once share 0.066 |
| 01.duplicated_blocks | little shipping code is repeated verbatim across filesshare 0.0041 · product files 557 · distinct blocks 83,755 |
| 01.swallowed_errors | errors are rarely thrown awayloc 338,958 · files 1 · per kloc 0.0 |
| 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 2,750 |
| 05.security_guardrails | at least one standard guard rail is configured |
| 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.known_vulnerabilities | no locked dependency has a published advisoryadvisories 0 · dependencies 6 · 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_manifest_conflict | manifest and licence file agree on MITlicense MIT |
| 05.license_vendored_unlicensed | no vendored third-party code is committedcomponents 0 |
| 05.license_grant_unclear | the licence is recognisable as MITclass permissive · license MIT |
| 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 47 · added in two years 7 · 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 |
| 04.releases_stopped | releases keep pace with developmentmedian gap days 0.0 · days since last tag 33 · commits last 90 days 315 |
| 04.release_branch | the newest release was cut from the branch surveyedelsewhere 71 · on branch 74 · tags in window 145 |
| 03.single_maintainer | no file says one person maintains itstatements 0 |
Could not conclude, or did not apply — 35
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.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 |
| 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.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 |
| 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 |
| 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: 2 records name PhpSpreadsheet with nothing tying them to this repository (CVE-2025-58051, CVE-2026-86020) |
| 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 8N4J-6H2M-D2DC 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/8N4J6H2MD2DC?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: 83.0authenticated: False |
| 15.7s | cloned the repository to a temporary directory | depth: full |
| 24.9s | read the git history | commits: 6812tracked files: 3547 |
| 132.2s | ran the deterministic checks | blame pass: Falseread working tree: False |
| 132.2s | recorded where this scan ran | attested: Falseenvironment: cloud-run |
| 200.1s | kept the facts, never the source, for re-reading under new checks | |
| 200.1s | deleting the working copy |
Total 200.1s ·source content sent off this machine: none · calls to a language model: 0 · the clone was deleted when the survey ended
An automated reading of a repository's code and its history up to one commit, with public advisory records. It may be wrong, it is not legal, financial, investment or security advice, and it does not replace diligence by a qualified person. It is provided for information: nobody may rely on it (Borehole's terms, section 3).