e54e63c · 50,000 commits · 9,371 files
Issued 2026-10-03
Nothing significant. Questions worth asking about Security & Reliability Posture, Engineering Process & SDLC Maturity.
104 checks ran across 6 assessable dimensions. 2 findings are worth checking first. 15 findings, each with evidence. One dimension cannot be assessed without an acquirer.
- 2 submodule(s) this survey does not read: ghost/core/content/themes/casper, ghost/core/content/themes/source .gitmodules:1
Borehole's proprietary scoring is calibrated across hundreds of repositories. Each finding here reads significant, but its check has not yet held up often enough in that calibration to rate significant on its own. If one holds when someone checks it, it is significant.
- 2 findings from checks Borehole's calibration found wrong more often than right are no longer published.
- The file and line of 3 credential-shaped matches are withheld. File and line are shown to whoever GitHub says controls this repository, signed in, and to a buyer of this report.
| Dimension | Rating | ||
|---|---|---|---|
| 01 | Architecture & Codebase — including AI provenance | strong | |
| 02 | Engineering Process & SDLC Maturity | adequate | |
| 03 | Organization & Key-Person Risk | strong | |
| 04 | Product & Engineering Maturity | adequate | |
| 05 | Security & Reliability Posture | adequate | |
| 06 | Observability & Operations | adequate | |
| 07 | Fit with the Acquirer | not assessable |
- 7% 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 ↑koenig/kg-simplemde/debug/simplemde.js is 16,902 lines, 234× this codebase's median file
adequateThe median source file here is 72 lines. 33 files exceed 1,000 lines, the largest being 16,902. 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. Measured against its own codebase's median, it is larger than 93% of 382 surveyed projects' largest files.
A note that does not affect this rating: notes like it are common in well-run projects.
| line-count | koenig/kg-simplemde/debug/simplemde.js:1 — 16,902 lines (234× median) |
| line-count | apps/shade/src/components/patterns/filters.tsx:1 — 3,537 lines (49× median) |
| line-count | apps/activitypub/src/views/preferences/components/dots-pattern.tsx:1 — 3,374 lines (46× median) |
| line-count | apps/activitypub/src/hooks/use-activity-pub-queries.ts:1 — 3,010 lines (41× median) |
| line-count | ghost/core/core/server/services/members/members-api/repositories/member-repository.js:1 — 2,733 lines (37× 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 ↑1 committed .only switches other tests off
adequate1 test file commits a focused `.only`, which runs that test and silently skips the rest of its suite. 29 skip markers across 15 of 3022 test files. Each is a failure somebody chose to stop seeing; the question is whether anyone is tracking them.
| koenig/koenig-lexical/test/e2e/selection.test.ts | koenig/koenig-lexical/test/e2e/selection.test.ts:107 — committed .only: other tests do not run |
| apps/ember-admin/tests/acceptance/editor-test.js | apps/ember-admin/tests/acceptance/editor-test.js:202 — skipped test |
| apps/ember-admin/tests/acceptance/editor-test.js | apps/ember-admin/tests/acceptance/editor-test.js:542 — skipped test |
| apps/ember-admin/tests/acceptance/error-handling-test.js | apps/ember-admin/tests/acceptance/error-handling-test.js:32 — skipped test |
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.
Tests are retried until they pass
adequateThe suite is configured to retry failing tests (apps/comments-ui/playwright.config.ts). A retry turns a flaky test green without saying why it failed, so a green build means the tests passed eventually. Ask how many retries a typical run needs, and which tests need them.
A note that does not affect this rating: notes like it are common in well-run projects.
| apps/comments-ui/playwright.config.ts | apps/comments-ui/playwright.config.ts:15 — test retry |
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 · strong · ratings ↑No finding. 10 checks ran and none fired; the rejection log below says why each did not.
Product & Engineering Maturity
04 · adequate · ratings ↑170 direct dependencies in a single manifest
adequate worth checking firstghost/core/package.json declares 170 direct dependencies. Each one is a maintenance obligation, a supply-chain surface and a potential licence question that transfers with the asset. The count says nothing about whether any given dependency was a good choice; it says how many such choices a buyer inherits.
The check that found this reads significant, but it has not yet held up often enough in Borehole's calibration to rate a finding significant on its own. Opening ghost/core/package.json and the 3 other files it cites settles it. If it holds when someone checks it, this finding is significant.
| direct-dependencies | ghost/core/package.json — 170 declared |
| direct-dependencies | apps/admin/package.json — 56 declared |
| direct-dependencies | apps/shade/package.json — 45 declared |
| direct-dependencies | apps/comments-ui/package.json — 16 declared |
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 ↑3 credential-shaped strings in the tree sit in tests, examples, documentation or local development settings
adequateStrings shaped like credentials appear only where fakes are usual: test fixtures, examples, documentation, placeholders and local stacks. They are almost always fakes. Ask someone to confirm that none of them works anywhere, because a real key in a development file is still a real key. 4 other matchs set aside: expired tokens, licence tokens a vendor verifies with a public key, or placeholder text where a key would go. None grants access to anything.
| Stripe live key | 3 cited: Stripe live key, where fakes are usual |
| File and line are shown to whoever GitHub says controls this repository, signed in, and to a buyer of this report. |
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.
4 Dockerfiles run the application as root
adequateNo USER instruction switches away from root, so the process runs with full privileges inside the container. It is a one-line fix and an ordinary expectation, which is why its absence is worth asking about: it usually says more about whether anyone has reviewed the deployment than about this container specifically.
| no-USER-instruction | docker/fake-mailgun/Dockerfile — runs as root |
| no-USER-instruction | docker/ghost-dev/Dockerfile — runs as root |
| no-USER-instruction | docker/tb-cli/Dockerfile — runs as root |
| no-USER-instruction | docker/tinybird-local-slim/Dockerfile — runs as root |
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.
32 locked dependencies have published vulnerabilities, 18 high or critical in what ships
adequate worth checking first32 of 4,267 locked dependencies match 66 published advisories in OSV, 37 of them rated high or critical. 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.
The check that found this reads significant, but it has not yet held up often enough in Borehole's calibration to rate a finding significant on its own. Opening pnpm-lock.yaml settles it. If it holds when someone checks it, this finding is significant.
| pnpm-lock.yaml | pnpm-lock.yaml — babel-traverse 6.26.0: GHSA-67hx-6x53-jw92 (critical); a development dependency |
| pnpm-lock.yaml | pnpm-lock.yaml — axios 1.18.1: GHSA-3pq3-5fj3-cg6v (high), fixed in 1.20.0 |
| pnpm-lock.yaml | pnpm-lock.yaml — brace-expansion 5.0.9: GHSA-6j4f-fj2g-mc7p (high), fixed in 5.0.10 |
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 production build publishes source maps
adequateThe build configuration emits source maps for production, so the original source, with its comments and structure, is downloadable by every visitor. Upload them to an error tracker and keep them off the public server instead.
| apps/admin-x-framework/vite.config.ts | apps/admin-x-framework/vite.config.ts:23 — source maps in a production build |
| apps/shade/vite.config.ts | apps/shade/vite.config.ts:27 — source maps in a production build |
| koenig/kg-unsplash-selector/vite.config.ts | koenig/kg-unsplash-selector/vite.config.ts:17 — source maps in a production build |
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 environment files are committed
adequateapps/comments-ui/.env, apps/portal/.env are tracked in git. Environment files are where credentials usually live, and committing one usually means nobody decided how secrets reach the running application. Whatever is in it is in the history for good. Check 05.1 says whether it holds anything credential-shaped.
A note that does not affect this rating: in Borehole's calibration, this check's notes were usually true but overstated.
| apps/comments-ui/.env | apps/comments-ui/.env — committed environment file |
| apps/portal/.env | apps/portal/.env — committed environment 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.
The build runs third-party code it does not pin
adequate1 step pipes a download straight into a shell. 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/tinybird.yml | .github/workflows/tinybird.yml:92 — download piped into a shell |
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 SQL statements built from strings
adequate2 places in product code build SQL by formatting or joining strings rather than passing parameters. 1 of them put a value into the string; in the rest, what the code shows going in is a table or column name, a constant, or something the line does not show. Ask whether any value reaches these strings, rather than a parameter.
A note that does not affect this rating: in Borehole's calibration, this check's notes were usually true but overstated.
| ghost/core/core/server/services/email-analytics/lib/queries.ts | ghost/core/core/server/services/email-analytics/lib/queries.ts:418 — SQL built from a string |
| ghost/core/core/server/models/comment.js | ghost/core/core/server/models/comment.js:25 — SQL built from a string |
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.
76 places insert HTML from a variable without sanitising it
adequate76 places set HTML from a value that is neither a literal nor passed through a sanitiser. Where the value can come from a user, that is stored cross-site scripting, and it is the first thing a buyer's security review looks for in a frontend.
A note that does not affect this rating: in Borehole's calibration, this check's notes were usually true but overstated.
| apps/activitypub/src/utils/content-formatters.ts | apps/activitypub/src/utils/content-formatters.ts:174 — HTML from a variable |
| apps/activitypub/src/utils/content-formatters.ts | apps/activitypub/src/utils/content-formatters.ts:213 — HTML from a variable |
| apps/activitypub/src/utils/content-formatters.ts | apps/activitypub/src/utils/content-formatters.ts:234 — HTML from a variable |
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.
71 advisories against this project in the last 24 months, 26 high or critical
adequateThe newest was published on 2026-10-01. A project that publishes advisories is telling its users about its fixes, and the count and pace say how much security work it carries. Whether 6 of them are fixed in the code you ship could not be told from this history: its version is only known to be at least 6.65.0. Answer lives in: the release you run, set against each fixed version.
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-fwh9-qg68-vxp4 | 2026-10-01: GHSA-fwh9-qg68-vxp4 (moderate), fixed in 6.67.0: Regular Expression Denial of Service in Content Import |
| GHSA-9m4w-fmjw-fvjq | 2026-10-01: GHSA-9m4w-fmjw-fvjq (moderate), fixed in 6.67.0: Regular Expression Denial of Service in External Media Inliner |
| GHSA-hqq2-xqr2-fmx2 | 2026-10-01: GHSA-hqq2-xqr2-fmx2 (moderate), fixed in 6.67.0: Stored XSS via SVG Files in Content Imports |
| GHSA-69qc-f5m6-889c | 2026-10-01: GHSA-69qc-f5m6-889c (high), fixed in 6.67.0: Stored XSS via Embed Card Previews |
| GHSA-788w-68h3-cvxp | 2026-10-01: GHSA-788w-68h3-cvxp (high), fixed in 6.67.0: Remote Code Execution via Bookmark Card Images |
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 ↑No structured logging library is in use
adequateNothing references a structured logging library. Logs that are written to be read by a person are not searchable by a machine, which means incident response here is proportional to how well someone remembers the codebase rather than to what the tooling can find.
| logging-scan | searched 7,885 files for 10 structured logging libraries; 0 matched |
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 code branches on the environment's name at 17 places
adequate17 places outside configuration test whether they are running in production or staging. Staging then does not exercise production's code, and each deploy is the first run of those branches. Differences belong in configuration the code reads, not in the code.
A note that does not affect this rating: in Borehole's calibration, this check's notes were usually true but overstated.
| apps/ember-admin/ember-cli-build.js | apps/ember-admin/ember-cli-build.js:15 — branch on the environment name |
| apps/ember-admin/ember-cli-build.js | apps/ember-admin/ember-cli-build.js:15 — branch on the environment name |
| apps/ember-admin/ember-cli-build.js | apps/ember-admin/ember-cli-build.js:54 — branch on the environment name |
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
8 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 (ghost/core/core/server/data/tinybird/ARCHITECTURE.md). Does it match what the team believes today? Ask them to walk through it against the code.
- measured The repository pulls code in through git submodules (.gitmodules). A buyer receives pointers, not that code. Can every submodule be fetched without the team's credentials, and who owns each one?
- Is the architecture right for the next three years of the product?
- Were the home-grown components reasonable choices when they were made, and are they now?
Engineering Process & SDLC Maturity
02 · high coverage- Is review real or a rubber stamp? Comment depth and time to approve need the pull request history.
- Is delivery planned and measured, or heroic?
- How are incidents run, reviewed and learned from?
Organization & Key-Person Risk
03 · partial coverage- measured 758 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 4,633 commits landed in the last year, against 3,074 the year before (+51%). 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- measured 05.1 and 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.
- measured No threat model is in the tree of what looks like a running service. Does one exist elsewhere, and who owns it?
- 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- measured Nothing in the tree backs up or restores data. How is data backed up, and has a restore ever been rehearsed?
- measured No alert rule is defined in the repository. Where are alerts defined, who receives them, and when did one last fire?
- 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 TypeScript codebase, with JavaScript alongside (47% of source files). Does your engineering organisation already run TypeScript in production, or would this be the first?
- The bulk of this system sits in ghost/, apps/, koenig/. Which of your existing systems would each of those have to absorb or replace?
- The repository carries deployment configuration (Dockerfile.production and 4 more). Does that match your deployment and on-call model, or does it need rehosting first?
- 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/tryghost/ghost/e54e63c)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 — 89 signals that ran and did not fire
Appendix: rejection log — 89 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 — 66
| 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 (30 Jul 2014 to 26 Sep 2026)files 45,408 · top5 share 0.027 · history read the most recent 50,000 commits (30 Jul 2014 to 26 Sep 2026) |
| 04.debt_markers | debt markers are sparsemarkers 405 · per kloc 0.34 · lines read 1,178,098 |
| 04.test_growth | test effort kept pace with code written, in the most recent 50,000 commits (30 Jul 2014 to 26 Sep 2026)history read the most recent 50,000 commits (30 Jul 2014 to 26 Sep 2026) · late test per code 1.025 · early test per code 0.688 |
| 04.churn_trend | rework is not rising against new work, in the most recent 50,000 commits (30 Jul 2014 to 26 Sep 2026)history read the most recent 50,000 commits (30 Jul 2014 to 26 Sep 2026) · late delete per insert 0.613 · early delete per insert 0.702 |
| 04.eol_runtime | every pinned runtime is still supportedeol as of 2026-09-24 |
| 04.fixes_with_tests | fixes usually come with a testfixes 1,608 · share 0.529 · with tests 851 |
| 04.fix_share_trend | fixing is not crowding out building |
| 04.compat_layers | little code is kept for the old wayshare 0.0 · code files 4,298 · compat files 2 |
| 04.dependency_redundancy | one library per job, mostly |
| 06.telemetry_presence | a telemetry or error-reporting library is referencednote presence only; whether anyone watches it is not visible here · matches 70 |
| 06.healthcheck_presence | a health or readiness check is defined |
| 06.correlation_ids | a request can be followed through the logstracing False · request id sites 7 |
| 06.error_reporting | an error reporter is initialisedinitialised 3 · config files 0 |
| 06.usage_reporting_default | the product's code names no reporting hostsettings on 0 · settings off 1 |
| 06.release_markers | releases are markedtags last year 105 · release commits 9 · changelog commits 41 |
| 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 758 · top share less than a quarter |
| 03.critical_path_ownership | more than one person changes the critical pathsauthors 227 |
| 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 15 · joined 22 · regular last year 42 |
| 02.merge_discipline | a meaningful share of recent change carries evidence of reviewmerges 58 · window last 24 months · with tracked 107 |
| 02.ci_presence | CI configuration is present in the working treecount 25 |
| 02.test_presence | tests are present in a normal proportion to sourcetests 2,502 · source 6,798 · test ratio 0.368 |
| 02.conventional_commits | commit subjects generally carry content, in the most recent 50,000 commits (30 Jul 2014 to 26 Sep 2026)sampled 47,459 · history read the most recent 50,000 commits (30 Jul 2014 to 26 Sep 2026) · low content share 0.03 |
| 02.branch_protection_hints | process scaffolding is present in the repository |
| 02.ci_runs_tests | CI invokes a test runnerconfigs 24 · with tests 2 |
| 02.ci_test_gating | no test run in CI is written so that it cannot failconfigs 25 |
| 02.revert_share | change is rarely undoneshare 0.006 · reverts 49 · recent commits 7,719 |
| 02.dependency_update_cadence | dependencies move with the codelockfiles 2 · commits since 1 · days since lockfile changed 0 |
| 02.lint_in_build | a linter or formatter runs in the buildwired 51 · ci configs 25 · product files 4,298 |
| 02.long_lived_branches | the typical branch reaches the trunk quicklyshare 0.0 · merges 50 · long lived 0 |
| 02.commit_size | changes arrive in reviewable sizesshare 0.017 · commits 7,431 · over 2000 lines 128 |
| 01.burst_import | no commit run met both the rate and the net-addition threshold, in the most recent 50,000 commits (30 Jul 2014 to 26 Sep 2026)gap seconds 180 · history read the most recent 50,000 commits (30 Jul 2014 to 26 Sep 2026) · min add ratio 3.0 |
| 01.message_uniformity | commit subjects vary in wording and length, in the most recent 50,000 commits (30 Jul 2014 to 26 Sep 2026)history read the most recent 50,000 commits (30 Jul 2014 to 26 Sep 2026) · length stdev 16.99 · repeat share 0.17 |
| 01.duplicated_blocks | little shipping code is repeated verbatim across filesshare 0.0116 · product files 4,295 · distinct blocks 313,223 |
| 01.swallowed_errors | errors are rarely thrown awayloc 1,185,913 · files 1 · per kloc 0.01 |
| 01.build_reproducibility | every base image names a versionfloating 0 · from lines 5 |
| 01.unfinished_migration | JavaScript to TypeScript: the move is still under way: the new language's share rose in the last yearmigration JavaScript to TypeScript · new share now 0.551 · new share at start 0.0 |
| 01.weights_in_git | no model weights are committedfiles 0 |
| 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.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.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.public_env_secret | only publishable values carry a public prefixnames 0 · sites 0 · not secrets 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 3 |
| 05.license_manifest_conflict | manifest and licence file agree on MITlicense MIT |
| 05.license_vendored_unlicensed | all 1 vendored components state their terms, in a licence file, their own headers or a notices filecomponents 1 · stated in headers or notices 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.flags_accumulating | flags are retired about as fast as they are addedlive 24 · retired 34 · flags seen 58 |
| 04.deprecations_lingering | few deprecations have outlived two yearsolder than two years 3 · files with deprecations 40 |
| 04.dependency_churn | few dependencies were added and dropped within 60 daysdependencies seen 351 · added in two years 155 · removed within 60 days 8 |
| 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 -4 · commits last 90 days 1,870 |
| 04.release_branch | the newest release, v6.67.0, was made after the surveyed commit on the branch surveyed, in the most recent 50,000 commits (30 Jul 2014 to 26 Sep 2026)elsewhere 77 · on branch 940 · history read the most recent 50,000 commits (30 Jul 2014 to 26 Sep 2026) |
| 03.single_maintainer | no file says one person maintains itstatements 0 |
Could not conclude, or did not apply — 23
Not a clean result. Each says why it could not answer here.
| Signal | Why |
|---|---|
| 04.schema_churn | columns, once added, stay |
| 06.print_logging | a frontend: console output is the browser's, not the server's |
| 06.alert_rules | no alert rules in the repository; they may live in a console |
| 06.deployed_image_floats | no deployment descriptor names an image |
| 06.probes_identical | no Kubernetes probes |
| 06.single_replica | no Kubernetes deployments |
| 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 (30 Jul 2014 to 26 Sep 2026) were read |
| 03.knowledge_silos | not assessed: this check needs the whole history, and only the most recent 50,000 commits (30 Jul 2014 to 26 Sep 2026) were read |
| 03.drive_by_contributors | not assessed: this check needs the whole history, and only the most recent 50,000 commits (30 Jul 2014 to 26 Sep 2026) were read |
| 03.contributor_attrition | not assessed: this check needs the whole history, and only the most recent 50,000 commits (30 Jul 2014 to 26 Sep 2026) were read |
| 02.release_cadence | not assessed: this check needs the whole history, and only the most recent 50,000 commits (30 Jul 2014 to 26 Sep 2026) were read |
| 01.initial_dump | not assessed: this check needs the whole history, and only the most recent 50,000 commits (30 Jul 2014 to 26 Sep 2026) were read |
| 01.revision_depth | not assessed: this check needs the whole history, and only the most recent 50,000 commits (30 Jul 2014 to 26 Sep 2026) were read |
| 01.notebook_outputs | not a data or machine-learning repository |
| 05.outbound_timeouts | not assessed for JavaScript or TypeScript, the languages the product is written in: this check's patterns read other languages only |
| 05.migration_reversibility | too few migrations to judge |
| 05.resource_limits | no Kubernetes workload manifests |
| 05.cleartext_traffic | not a mobile app |
| 05.dataset_provenance | not a data or machine-learning repository |
| 04.api_versions_coexisting | one API version is served, or none |
| 05.project_advisories | record incomplete: no advisory found in the sources that answered; OSV npm @tryghost/admin-toolbar (an empty record for a package published here), OSV npm @tryghost/announcement-bar (an empty record for a package published here), OSV npm @tryghost/comments-ui (an empty record for a package published here), OSV npm @tryghost/signup-form (an empty record for a package published here), OSV npm @tryghost/sodo-search (an empty record for a package published here), OSV npm @tryghost/kg-card-factory (an empty record for a package published here), OSV npm @tryghost/kg-clean-basic-html (an empty record for a package published here), OSV npm @tryghost/kg-converters (an empty record for a package published here), OSV npm @tryghost/kg-default-cards (an empty record for a package published here), OSV npm @tryghost/kg-default-nodes (an empty record for a package published here), OSV npm @tryghost/kg-default-transforms (an empty record for a package published here), OSV npm @tryghost/kg-html-to-lexical (an empty record for a package published here), OSV npm @tryghost/kg-lexical-html-renderer (an empty record for a package published here), OSV npm @tryghost/kg-markdown-html-renderer (an empty record for a package published here), OSV npm @tryghost/kg-simplemde (an empty record for a package published here), OSV npm @tryghost/kg-unsplash-selector (an empty record for a package published here), OSV npm @tryghost/kg-utils (an empty record for a package published here), OSV npm @tryghost/koenig-lexical (an empty record for a package published here), OSV npm @tryghost/adapter-base-cache (an empty record for a package published here), OSV npm @tryghost/adapter-base-scheduling (an empty record for a package published here), OSV npm @tryghost/adapter-base-sso (an empty record for a package published here), OSV npm ghost-storage-base (an empty record for a package published here), NVD did not |
| 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 Q53H-5AME-F282 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/Q53H5AMEF282?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-03 · shown | borehole 0.7.11 | 17 | adequate |
12 other readings (show)
| 2026-10-04 | borehole 0.7.13 | 17 | adequate |
| 2026-10-03 | borehole 0.7.12 | 17 | adequate |
| 2026-10-02 | borehole 0.7.10 | 17 | adequate |
| 2026-10-01 | borehole 0.7.9 | 17 | adequate |
| 2026-09-30 | borehole 0.7.8 | 17 | adequate |
| 2026-09-29 | borehole 0.7.6 | 18 | adequate |
| 2026-09-28 | borehole 0.7.5 | 17 | adequate |
| 2026-09-28 | borehole 0.7.4 | 17 | adequate |
| 2026-09-27 | borehole 0.7.3 | 16 | adequate |
| 2026-09-27 | borehole 0.7.2 | 16 | adequate |
| 2026-09-27 | borehole 0.7.1 | 16 | adequate |
| 2026-09-26 | borehole 0.7.0 | 16 | adequate |
Where this scan ran
This scan ran on ordinary cloud infrastructure (cloud-run), not in a hardware-isolated confidential VM. Nothing about it is attested by Google.
What an attested survey proves, and what it does not.
What this scan did with the repository — 7 steps
Written by the steps themselves as they ran, not described afterwards. A hand-written account of a data flow drifts the first time somebody changes the flow and not the account.
| At | Step | Detail |
|---|---|---|
| 0.0s | read repository metadata from the GitHub API | authenticated: False |
| 92.0s | cloned the repository to a temporary directory | depth: full |
| 178.5s | read the git history | commits: 50000tracked files: 9371 |
| 718.5s | ran the deterministic checks | blame pass: Falseread working tree: False |
| 718.6s | recorded where this scan ran | attested: Falseenvironment: cloud-run |
| 1087.3s | kept the facts, never the source, for re-reading under new checks | |
| 1087.3s | deleting the working copy |
Total 1087.3s ·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).