6e8697b · 4,392 commits · 591 files
Issued 2026-10-01
Significant: one contributor carries the recent work.
1 of 6 assessable dimensions carries significant findings, 1 is adequate and 3 are strong. 7 findings, each with its evidence: the commit, path and lines it rests on, or, when something is missing, what was looked for. One dimension cannot be assessed without an acquirer.
- 03.1 Significant: Bus factor 1: recent work is concentrated in one contributor
- Words about people are today's: bands rather than exact shares, dates or day counts, and what the history measured rather than why.
- 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 | significant findings | |
| 04 | Product & Engineering Maturity | strong | |
| 05 | Security & Reliability Posture | adequate | |
| 06 | Observability & Operations | not assessable | |
| 07 | Fit with the Acquirer | not assessable |
- 1% 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 591 of 591 counted files
Architecture & Codebase — including AI provenance
01 · strong · ratings ↑No finding. 11 checks ran and none fired; the rejection log below says why each did not.
Engineering Process & SDLC Maturity
02 · strong · ratings ↑No finding. 16 checks ran and none fired; the rejection log below says why each did not.
Organization & Key-Person Risk
03 · significant findings · ratings ↑Bus factor 1: recent work is concentrated in one contributor
significant findingsIn the last 24 months, one contributor authored three-quarters or more of 125 non-merge commits among 6 authors; across all history, a quarter or more of 3,494. This is the single most expensive thing to discover after closing, and the repository cannot tell you whether that person is part of the transaction.
| git shortlog -sn | last 24 months: top author three-quarters or more of 125 commits; bus factor 1; 6 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 a year
adequateOne person authored a quarter or more of 3,494 commits and has not committed here for more than a year, 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 a year ago, measured to the survey |
| git shortlog -sn | top author a quarter or more of 3,494 commits |
Respond to this finding
Your response is published beside the finding, not instead of it. A finding you can argue with is the point — and a wrong one is calibration data we want.
An owner's response is removed only when it is unlawful, impersonates someone, publishes personal data or a credential, or is not about the finding. Disagreeing with the report is never a reason. To report a response, or to reach us about one, write to takedown@borehole.dev.
The next contributor after the top one has not committed here for more than a year
adequateThe #2 contributor of the last three years (less than a quarter of the commits) has not committed here for more than a year, while the repository is still active. These are the people a buyer assumes would step up if the top contributor stopped. The history shows only that no commits of theirs landed here, not why.
| git shortlog -sn | the #2 contributor of the last three years (less than a quarter of the commits) has not committed here for more than a year |
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 ↑Effort is shifting from building to rewriting
adequateDeleted lines per line added rose from 0.86 to 1.20 between the first and second halves of this history. Rework is normal and often healthy, but a rising ratio means an increasing share of the team's time is spent replacing code that already exists rather than building what does not. Whether that is deliberate repayment or churn is a question for the team.
A note that does not affect this rating: in Borehole's calibration, this check's notes were usually true but overstated.
| deletions-per-insertion | first half 0.86, second half 1.20 (split 2017-11-14) |
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 ↑The build runs third-party code it does not pin
adequate3 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.
| .github/workflows/ci.yml | .github/workflows/ci.yml:73 — action pinned by tag |
| .github/workflows/lock.yml | .github/workflows/lock.yml:19 — 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.
Licence text does not match a standard licence
adequateLICENSE.md 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.md | LICENSE.md:1 — 10 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.
1 advisory against this project in the last 24 months, 1 high or critical
adequateThe newest was published on 2026-03-13. 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.
| GHSA-rvv3-g6hj-g44x | 2026-03-13: GHSA-rvv3-g6hj-g44x (high), fixed in 15.1.1: Denial of Service (DoS) via Uncontrolled Recursion |
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- 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 a quarter or more of the commits in this history. Is that person part of the transaction, and for how long after it?
- 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 91 commits landed in the last year, against 34 the year before (+168%). 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 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 C# codebase. Does your engineering organisation already run C# in production, or would this be the first?
- The bulk of this system sits in 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/luckypennysoftware/automapper/6e8697b)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 — 97 signals that ran and did not fire
Appendix: rejection log — 97 signals that ran and did not fire
Published on purpose. A signal that looked and decided not to fire has told you something, and this is the calibration data behind every threshold above.
Looked, and found nothing — 61
| Signal | What it found |
|---|---|
| 04.hotspot_concentration | change is spread across the codebase rather than pooling in a few filesfiles 3,024 · top5 share 0.071 |
| 04.debt_markers | debt markers are sparsemarkers 1 · per kloc 0.01 · lines read 69,773 |
| 04.test_growth | test effort kept pace with code writtenlate test per code 1.881 · early test per code 0.658 |
| 04.compat_layers | little code is kept for the old wayshare 0.011 · code files 92 · 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 579 |
| 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 197 · active 12mo 3 |
| 03.drive_by_contributors | an open contributor base, where one-commit contributors are normalauthors 197 · one off share 0.563 |
| 03.critical_path_ownership | more than one person changes the critical pathsauthors 6 |
| 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 44 · window last 24 months · with tracked 4 |
| 02.ci_presence | CI configuration is present in the working treecount 4 |
| 02.test_presence | tests are present in a normal proportion to sourcetests 421 · source 513 · test ratio 0.821 |
| 02.release_cadence | tags are presenttags 69 |
| 02.conventional_commits | commit subjects generally carry contentsampled 3,497 · low content share 0.136 |
| 02.branch_protection_hints | process scaffolding is present in the repository |
| 02.skipped_tests | few tests are switched offfocused 0 · skipped 0 · test files 426 |
| 02.ci_test_gating | no test run in CI is written so that it cannot failconfigs 4 |
| 02.revert_share | change is rarely undoneshare 0.008 · reverts 1 · recent commits 125 |
| 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.128 · merges 39 · long lived 5 |
| 02.commit_size | changes arrive in reviewable sizesshare 0.008 · commits 118 · over 2000 lines 1 |
| 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 54,333 · share of insertions 0.0598 |
| 01.message_uniformity | commit subjects vary in wording and lengthlength stdev 32.72 · repeat share 0.186 |
| 01.revision_depth | most files were revisited after they were first writtenfiles seen 109 · write once share 0.073 |
| 01.oversized_modules | no module is an outlier against this codebase's own normlargest 3,389 · threshold 1,000 · median lines 48 |
| 01.duplicated_blocks | little shipping code is repeated verbatim across filesshare 0.0019 · product files 92 · distinct blocks 6,978 |
| 01.swallowed_errors | errors are rarely thrown awayloc 69,995 · files 0 · 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 579 |
| 05.security_guardrails | at least one standard guard rail is configured |
| 05.dependency_pinning | dependencies are substantially pinnedunpinned 0 |
| 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 849,403 |
| 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 9 · 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_vendored_unlicensed | no vendored third-party code is committedcomponents 0 |
| 05.committed_native_libraries | no widely used compiled library is committed to the productlibraries 0 |
| 04.deprecations_lingering | few deprecations have outlived two yearsolder than two years 0 · files with deprecations 14 |
| 04.dependency_churn | few dependencies were added and dropped within 60 daysdependencies seen 4 · added in two years 0 · 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 24.5 · days since last tag 92 · commits last 90 days 10 |
| 04.release_branch | the newest release was cut from the branch surveyedelsewhere 3 · on branch 62 · tags in window 65 |
| 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 1 |
| 05.project_exploited | no affecting advisory is on CISA's Known Exploited listexploited 0 |
Could not conclude, or did not apply — 36
Not a clean result. Each says why it could not answer here.
| Signal | Why |
|---|---|
| 04.dependency_sprawl | no dependency manifest of the product's own was found |
| 04.eol_runtime | no pinned runtime version to check |
| 04.fixes_with_tests | too few fixes in 24 months to judge |
| 04.fix_share_trend | fewer than six busy quarters to compare |
| 04.schema_churn | no schema migrations to read |
| 04.dependency_redundancy | no JavaScript manifest to read |
| 06.telemetry_depth | 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.knowledge_silos | too few substantial top-level directories to read ownership |
| 03.joiners_and_leavers | too few regular contributors to see a trend |
| 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.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 |
| 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 |
Anyone can check this report against the authoritative record — click the stamp, or enter S1CH-WZPB-FT0N 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/S1CHWZPBFT0N?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-10-01 · shown | borehole 0.7.9 | 9 | significant findings |
4 other readings (show)
| 2026-10-04 | borehole 0.7.13 | 10 | significant findings |
| 2026-10-03 | borehole 0.7.12 | 10 | significant findings |
| 2026-10-03 | borehole 0.7.11 | 10 | significant findings |
| 2026-10-02 | borehole 0.7.10 | 10 | significant findings |
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: 124.5authenticated: False |
| 6.3s | cloned the repository to a temporary directory | depth: full |
| 9.3s | read the git history | commits: 4392tracked files: 591 |
| 69.2s | ran the deterministic checks | blame pass: Trueread working tree: False |
| 69.2s | recorded where this scan ran | attested: Falseenvironment: cloud-run |
| 95.1s | kept the facts, never the source, for re-reading under new checks | |
| 95.1s | deleting the working copy |
Total 95.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).