9a34acf · 6,170 commits · 214 files
Issued 2026-09-24
Nothing significant. Questions worth asking about Security & Reliability Posture, Architecture & Codebase — including AI provenance.
43 checks ran across 6 assessable dimensions. None found a significant problem; 4 raised something worth a question. 5 findings, each with evidence. One dimension cannot be assessed without an acquirer.
- Words about people are today's: bands rather than exact shares, dates or day counts, and what the history measured rather than why.
| Dimension | Rating | ||
|---|---|---|---|
| 01 | Architecture & Codebase — including AI provenance | adequate | |
| 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 | strong | |
| 07 | Fit with the Acquirer | not assessable |
- 2% 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 212 of 214 counted files
Architecture & Codebase — including AI provenance
01 · adequate · ratings ↑lib/response.js is 1,050 lines, 14× this codebase's median file
adequateThe median source file here is 75 lines. 1 file exceed 1,000 lines, the largest being 1,050. 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 | lib/response.js:1 — 1,050 lines (14× median) |
Respond to this finding
Your response is published beside the finding, not instead of it. A finding you can argue with is the point — and a wrong one is calibration data we want.
An owner's response is removed only when it is unlawful, impersonates someone, publishes personal data or a credential, or is not about the finding. Disagreeing with the report is never a reason. To report a response, or to reach us about one, write to takedown@borehole.dev.
Engineering Process & SDLC Maturity
02 · adequate · ratings ↑Almost no process scaffolding exists in the repository
adequateOf five ordinary markers — CI workflows, CODEOWNERS, a pull-request template, pre-commit hooks, contribution guidance — 1 is present: CI workflows. Branch protection itself is a GitHub setting rather than a file, so this is a reading of proxies and not of the rules themselves. What it does establish is that the process is not written down anywhere a new engineer would find it.
| process-scaffolding | 1 of 5 markers present across 214 tracked files |
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 ↑The contributor who wrote more than half of this has not committed here for more than three years
adequateOne person authored more than half of 5,685 commits and has not committed here for more than three 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 three years ago, measured to the survey |
| git shortlog -sn | top author more than half of 5,685 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. 6 checks ran and none fired; the rejection log below says why each did not.
Security & Reliability Posture
05 · adequate · ratings ↑37 dependencies float, and no lockfile is committed
adequateDependency versions are declared as ranges and no lockfile is committed, so a build today does not necessarily produce what a build last month produced. That matters twice over in a transaction: the thing being bought cannot be reproduced exactly, and a compromised upstream release arrives without anyone choosing to take it.
| unpinned | package.json — accepts ^2.0.0 |
| unpinned | package.json — body-parser ^2.3.0 |
| unpinned | package.json — content-disposition ^2.0.1 |
| unpinned | package.json — content-type ^2.0.0 |
| unpinned | package.json — cookie ^0.7.1 |
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.
Licence text does not match a standard licence
adequateLICENSE exists but its text does not match any standard licence. A bespoke or hand-edited licence is not wrong, but it cannot be cleared by recognising its name: counsel has to read it, and until they do neither side knows precisely what rights transfer with the code.
| LICENSE | LICENSE:1 — 24 lines, unrecognised |
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 · strong · ratings ↑No finding. 3 checks ran and none fired; the rejection log below says why each did not.
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.
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- 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 One contributor authored more than half of the commits in this history. Is that person part of the transaction, and for how long after it?
- measured The repository went quiet for 3 months, from November 2023 to February 2024, then 45 commits landed in the six weeks after. Where was the work of that period done, and is it in this history? The history shows the gap, not why it happened.
- 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 51 commits landed in the last year, against 88 the year before (-42%). Is that maintenance mode, a pivot, or fewer people working on it? The count looks the same for all three.
- 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 JavaScript codebase. Does your engineering organisation already run JavaScript in production, or would this be the first?
- The bulk of this system sits in lib/, bin/, support/. 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/expressjs/express/9a34acf)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 — 38 signals that ran and did not fire
Appendix: rejection log — 38 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 — 32
| Signal | What it found |
|---|---|
| 04.hotspot_concentration | change is spread across the codebase rather than pooling in a few filesfiles 1,039 · top5 share 0.206 |
| 04.debt_markers | debt markers are sparsemarkers 0 · per kloc 0.0 · lines read 26,341 |
| 04.dependency_sprawl | direct dependency counts are unremarkable |
| 04.test_growth | test effort kept pace with code writtenlate test per code 2.228 · early test per code 0.444 |
| 04.churn_trend | rework is not rising against new worklate delete per insert 0.447 · early delete per insert 0.828 |
| 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 164 |
| 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 |
| 03.contributor_concentration | no single contributor dominates the last 24 monthsyears 17.2 · window last 24 months · authors 393 |
| 03.active_contributors | more than one contributor active in the trailing yearall time 394 · active 12mo 36 |
| 03.knowledge_silos | every substantial directory has been touched by more than one personauthors 394 · directories 7 |
| 03.drive_by_contributors | an open contributor base, where one-commit contributors are normalauthors 394 · one off share 0.759 |
| 02.merge_discipline | a meaningful share of recent change carries evidence of reviewmerges 0 · window last 24 months · with tracked 0 |
| 02.ci_presence | CI configuration is present in the working treecount 5 |
| 02.test_presence | tests are present in a normal proportion to sourcetests 91 · source 141 · test ratio 0.645 |
| 02.release_cadence | tags are presenttags 305 |
| 02.conventional_commits | commit subjects generally carry contentsampled 5,685 · low content share 0.103 |
| 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 111 |
| 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.007 · reverts 1 · recent commits 139 |
| 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 92 · share of insertions 0.0007 |
| 01.message_uniformity | commit subjects vary in wording and lengthlength stdev 17.55 · repeat share 0.161 |
| 01.revision_depth | most files were revisited after they were first writtenfiles seen 1,042 · write once share 0.292 |
| 05.committed_secrets | no credential-shaped strings outside test and fixture pathsnote the working tree only; the history is 05.5 · patterns 7 · files read 164 |
| 05.security_guardrails | at least one standard guard rail is configured |
| 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 7 · truncated False · added lines 76,547 |
| 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 24 · pipe to shell 0 · unpinned third party 0 |
| 05.license_vendored_unlicensed | no vendored third-party code is committedcomponents 0 |
Could not conclude, or did not apply — 6
Not a clean result. Each says why it could not answer here.
| Signal | Why |
|---|---|
| 04.eol_runtime | no pinned runtime version to check |
| 02.dependency_update_cadence | no lockfile to date |
| 01.duplicated_blocks | too few source files to look for duplication across them |
| 05.container_runs_as_root | no Dockerfile to read |
| 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 | no licence file could be identified to compare the manifest against |
Anyone can check this report against the authoritative record — click the stamp, or enter PNCM-PTM2-F191 at borehole.dev/verify.
The code commits to the 43 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://staging.borehole.dev/verify/PNCMPTM2F191?via=badge)
5 pieces of evidence on this report quote the repository directly. Four checks quote text: up to five TODO-style comments, up to four commit subjects, up to five unpinned dependency lines and one status line from the README's first screen, such as “no longer maintained”. In each case the text is the evidence, which is why it is kept by default.
This rewrites every stored reading of this repository, and every later reading, including a re-read, is stored without the quoted text. The facts we keep to re-read it still hold the lines, as the privacy notice says. The pointers stay.
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-24 · shown | borehole 0.4.0.dev2 | 5 | adequate |
2 other readings (show)
| 2026-09-26 | borehole 0.7.0 | 7 | adequate |
| 2026-09-25 | borehole 0.6.1 | 6 | 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 — 6 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.4s | read repository metadata from the GitHub API | size mb: 9.7authenticated: False |
| 2.4s | cloned the repository to a temporary directory | depth: full |
| 3.9s | read the git history | commits: 6170tracked files: 214 |
| 10.4s | ran the deterministic checks | blame pass: Trueread working tree: False |
| 10.4s | recorded where this scan ran | attested: Falseenvironment: cloud-run |
| 10.4s | deleting the working copy |
Total 10.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).