c7bcd68 · 5,362 commits · 5,334 files
Issued 2026-10-28
Nothing significant. Questions worth asking about Security & Reliability Posture, Product & Engineering Maturity.
104 checks ran across 6 assessable dimensions. 1 finding is worth checking first. 12 findings, each with evidence. One dimension cannot be assessed without an acquirer.
- 04.61 No release for 35 months while development continues
- 05.60 Relicensed: AGPL-3.0 → Apache-2.0 (2022-11-16) LICENSE
- names Linux Foundation AGENTS.md:3
- states a policy on AI-generated contributions CONTRIBUTING.md:191
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.
- 05.26 82 locked dependencies have published vulnerabilities, 72 high or critical in what ships
- 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 | adequate | |
| 04 | Product & Engineering Maturity | adequate | |
| 05 | Security & Reliability Posture | adequate | |
| 06 | Observability & Operations | adequate | |
| 07 | Fit with the Acquirer | not assessable |
- 33% 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 ↑services/libs/common/src/constants/disposable-email-domains.ts is 8,011 lines, 160× this codebase's median file
adequateThe median source file here is 50 lines. 23 files exceed 1,000 lines, the largest being 8,011. 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 87% 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 | services/libs/common/src/constants/disposable-email-domains.ts:1 — 8,011 lines (160× median) |
| line-count | backend/src/services/integrationService.ts:1 — 3,502 lines (70× median) |
| line-count | services/apps/data_sink_worker/src/service/activity.service.ts:1 — 2,229 lines (44× median) |
| line-count | backend/src/database/repositories/memberRepository.ts:1 — 2,072 lines (41× median) |
| line-count | backend/src/database/repositories/organizationRepository.ts:1 — 1,833 lines (36× 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 ↑Regular contributors fell from 15 to 8 in a year
adequate6 people who committed regularly the year before made no commits in the last year, and 0 new regular contributors arrived. Ask whether the work they did is still covered.
| regular contributors by year | 15 then 8; 6 stopped committing, 0 began |
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 · adequate · ratings ↑90 direct dependencies in a single manifest
adequatebackend/package.json declares 90 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.
| direct-dependencies | backend/package.json — 90 declared |
| direct-dependencies | frontend/package.json — 35 declared |
| direct-dependencies | services/apps/packages_worker/package.json — 28 declared |
| direct-dependencies | services/apps/git_integration/pyproject.toml — 23 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.
13% of bug fixes add or change a test
adequateOf 907 fixes in the last 24 months, 114 touched a test. A fix without the test that would have caught the bug can quietly come back, and the suite never learns from what went wrong.
| fix commits touching tests | 114 of 907 |
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.
No release for 35 months while development continues
adequateThe last tag, v0.49.0, was cut 1072 days before the survey; the typical gap between releases was 7 days, and 678 commits landed in the last 90 days. Users run the last release, not this code.
| 89242fbd3 | last tag v0.49.0 |
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 ↑82 locked dependencies have published vulnerabilities, 72 high or critical in what ships
adequate worth checking first82 of 2,848 locked dependencies match 187 published advisories in OSV, 89 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 services/apps/mailing_list_integration/uv.lock and the 2 other files it cites settles it. If it holds when someone checks it, this finding is significant.
| services/apps/mailing_list_integration/uv.lock | services/apps/mailing_list_integration/uv.lock — certifi 2026.6.17: GHSA-6q48-6c7w-9gw2 (critical), fixed in 2026.10.18 |
| pnpm-lock.yaml | pnpm-lock.yaml — storybook 10.2.12: GHSA-f2ph-cmg5-wxc8 (critical), fixed in 10.6.2; a development dependency |
| services/apps/git_integration/uv.lock | services/apps/git_integration/uv.lock — dnspython 2.7.0: GHSA-45c3-73f7-pv4m (high), fixed in 2.9.0 |
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 environment files are committed
adequatebackend/.env.dist.composed, backend/.env.dist.local, frontend/.env.dist.composed and more 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.
| backend/.env.dist.composed | backend/.env.dist.composed — committed environment file |
| backend/.env.dist.local | backend/.env.dist.local — committed environment file |
| frontend/.env.dist.composed | frontend/.env.dist.composed — 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
adequate6 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; 1 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/backend-lint.yaml | .github/workflows/backend-lint.yaml:78 — action pinned by tag |
| .github/workflows/pr-title-lint.yml | .github/workflows/pr-title-lint.yml:14 — action pinned by tag |
| scripts/scaffold/temporal/Dockerfile | scripts/scaffold/temporal/Dockerfile:4 — 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.
20 SQL statements built from strings
adequate20 places in product code build SQL by formatting or joining strings rather than passing parameters. 4 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.
| backend/src/database/repositories/memberOrganizationRepository.ts | backend/src/database/repositories/memberOrganizationRepository.ts:60 — SQL built from a string |
| backend/src/database/repositories/memberRepository.ts | backend/src/database/repositories/memberRepository.ts:285 — SQL built from a string |
| backend/src/database/repositories/organizationRepository.ts | backend/src/database/repositories/organizationRepository.ts:528 — 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.
6 places insert HTML from a variable without sanitising it
adequate6 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.
| frontend/src/modules/activity/components/activity-content.vue | frontend/src/modules/activity/components/activity-content.vue:55 — HTML from a variable |
| frontend/src/modules/contributor/components/details/attributes/contributor-attribute-string.vue | frontend/src/modules/contributor/components/details/attributes/contributor-attribute-string.vue:4 — HTML from a variable |
| frontend/src/modules/contributor/components/details/overview/project/contributor-details-projects-affiliation.vue | frontend/src/modules/contributor/components/details/overview/project/contributor-details-projects-affiliation.vue:12 — 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.
Relicensed: AGPL-3.0 → Apache-2.0 (2022-11-16)
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".
| c640fa015 | LICENSE — AGPL-3.0 from 2022-08-25 |
| ac8e0511c | LICENSE — Apache-2.0 from 2022-11-16 |
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 ↑1343 commits in a year, and no release marked
adequateThe service took 1343 commits in the last year with no tag, no release commit and no changelog entry. What is running in production cannot be read from the repository, and a bug report cannot be mapped to a version. Ask how the team knows what is deployed.
| git tag; git log | no tag, release commit or changelog change in 12 months |
Respond to this finding
Your response is published beside the finding, not instead of it. A finding you can argue with is the point — and a wrong one is calibration data we want.
An owner's response is removed only when it is unlawful, impersonates someone, publishes personal data or a credential, or is not about the finding. Disagreeing with the report is never a reason. To report a response, or to reach us about one, write to takedown@borehole.dev.
Fit with the Acquirer
07 · not assessable · ratings ↑Not rated: structurally not assessable from a repository. What a person adds here.
Check it on the running system
4 checks against the running system follow from the findings above: what a buyer's engineer will try, how to run it first, and what to have ready. A paid survey of this repository includes them.
A paid survey of a public repository is also reviewed: a language model reads each finding against the code and withdraws only findings it judges the code contradicts, each listed with its reason. The review is a language model's reading of the findings against the code, and it can be wrong. It never adds a finding, never raises a band, and never removes a finding from a proven check or an advisory that affects the surveyed version.
What a person adds
The survey reads what the repository can show. The code cannot settle these questions, and on them this report states nothing. Each says where its answer lives: your own engineer, the company, or an assessor you choose can settle it. Questions marked measured open with something this repository shows.
Architecture & Codebase — including AI provenance
01 · full coverage- measured The tree carries design documentation (.claude/skills/adr/SKILL.md and 36 more). 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 57 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 1,341 commits landed in the last year, against 801 the year before (+67%). 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.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 Backup or restore tooling is in the tree (backend/src/database/migrations/V1691667297__restore-work-experience.sql). Has a restore ever been rehearsed, and how long did it take?
- 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. Does your engineering organisation already run TypeScript in production, or would this be the first?
- The bulk of this system sits in services/, backend/, frontend/. Which of your existing systems would each of those have to absorb or replace?
- The repository carries deployment configuration (backend/src/database/Dockerfile.flyway and 7 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/linuxfoundation/crowd.dev/c7bcd68)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 — 92 signals that ran and did not fire
Appendix: rejection log — 92 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 — 76
| Signal | What it found |
|---|---|
| 04.hotspot_concentration | change is spread across the codebase rather than pooling in a few filesfiles 10,295 · top5 share 0.02 |
| 04.debt_markers | debt markers are sparsemarkers 52 · per kloc 0.11 · lines read 484,953 |
| 04.test_growth | test effort kept pace with code writtenlate test per code 0.248 · early test per code 0.122 |
| 04.churn_trend | rework is not rising against new worklate delete per insert 0.59 · early delete per insert 0.565 |
| 04.eol_runtime | every pinned runtime is still supportedeol as of 2026-09-24 |
| 04.fix_share_trend | fixing is not crowding out building |
| 04.schema_churn | columns, once added, staydropped within 90 days 0 · columns added last year 87 |
| 04.compat_layers | little code is kept for the old wayshare 0.017 · code files 3,655 · compat files 61 |
| 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 24 |
| 06.structured_logging | a structured logging library is referencedmatches 12 |
| 06.healthcheck_presence | a health or readiness check is defined |
| 06.telemetry_depth | the service is visible in more than one way |
| 06.correlation_ids | a request can be followed through the logstracing True · request id sites 13 |
| 06.error_reporting | an error reporter is initialisedinitialised 1 · config files 0 |
| 06.usage_reporting_default | the product's code names no reporting hostsettings on 0 · settings off 0 |
| 06.environment_branching | environment differences live in configurationsites 10 |
| 06.migrate_on_start | migrations do not run at container start |
| 03.contributor_concentration | no single contributor dominates the last 24 monthsyears 4.2 · window last 24 months · authors 57 |
| 03.active_contributors | more than one contributor active in the trailing yearall time 57 · active 12mo 12 |
| 03.knowledge_silos | every substantial directory has been touched by more than one personauthors 57 · directories 4 |
| 03.drive_by_contributors | an open contributor base, where one-commit contributors are normalauthors 57 · one off share 0.351 |
| 03.contributor_attrition | no contributor dominates enough for their absence to matterauthors 57 · top share less than a quarter · top contributor last committed within the last three months |
| 03.critical_path_ownership | more than one person changes the critical pathsauthors 19 |
| 03.second_contributor_attrition | the second and third contributors are still active |
| 03.bus_factor_trend | the team has not narrowed to one person |
| 02.merge_discipline | a meaningful share of recent change carries evidence of reviewmerges 8 · window last 24 months · with tracked 0 |
| 02.ci_presence | CI configuration is present in the working treecount 8 |
| 02.test_presence | tests are present in a normal proportion to sourcetests 462 · source 4,117 · test ratio 0.112 |
| 02.release_cadence | tags are presenttags 54 |
| 02.conventional_commits | commit subjects generally carry contentsampled 5,165 · low content share 0.016 |
| 02.branch_protection_hints | process scaffolding is present in the repository |
| 02.ci_runs_tests | CI invokes a test runnerconfigs 8 · with tests 2 |
| 02.skipped_tests | few tests are switched offfocused 0 · skipped 0 · test files 468 |
| 02.ci_test_gating | no test run in CI is written so that it cannot failconfigs 8 |
| 02.revert_share | change is rarely undoneshare 0.001 · reverts 3 · recent commits 2,144 |
| 02.dependency_update_cadence | dependencies move with the codelockfiles 6 · commits since 6 · days since lockfile changed 0 |
| 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 7 · ci configs 8 · product files 3,655 |
| 02.commit_size | changes arrive in reviewable sizesshare 0.028 · commits 1,987 · over 2000 lines 55 |
| 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 390,850 · share of insertions 0.1478 |
| 01.message_uniformity | commit subjects vary in wording and lengthlength stdev 22.18 · repeat share 0.068 |
| 01.revision_depth | most files were revisited after they were first writtenfiles seen 4,400 · write once share 0.298 |
| 01.duplicated_blocks | little shipping code is repeated verbatim across filesshare 0.022 · product files 3,655 · distinct blocks 232,393 |
| 01.swallowed_errors | errors are rarely thrown awayloc 489,380 · files 3 · per kloc 0.01 |
| 01.build_reproducibility | every base image names a versionfloating 0 · from lines 2 |
| 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 4,628 |
| 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.container_runs_as_root | every shipped Dockerfile drops to a non-root user or builds on a non-root base imagedockerfiles 1 |
| 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.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.source_maps_shipped | production builds do not publish source mapssites 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.license_grant_unclear | the licence is recognisable as Apache-2.0class permissive · license Apache-2.0 |
| 05.committed_native_libraries | no widely used compiled library is committed to the productlibraries 0 |
| 04.api_versions_coexisting | one API version is served, or none |
| 04.deprecations_lingering | few deprecations have outlived two yearsolder than two years 0 · files with deprecations 4 |
| 04.dependency_churn | few dependencies were added and dropped within 60 daysdependencies seen 339 · added in two years 256 · removed within 60 days 3 |
| 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.release_branch | the newest release was cut from the branch surveyedelsewhere 2 · on branch 52 · tags in window 54 |
| 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 0 |
| 05.advisory_record | no advisory against the project in the last 24 monthscritical 0 · affecting 0 · could not tell 0 |
| 05.project_exploited | no affecting advisory is on CISA's Known Exploited listexploited 0 |
Could not conclude, or did not apply — 16
Not a clean result. Each says why it could not answer here.
| Signal | Why |
|---|---|
| 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 |
| 02.long_lived_branches | too few merges to judge (squash and rebase leave none) |
| 01.notebook_outputs | not a data or machine-learning repository |
| 05.outbound_timeouts | not assessed for TypeScript, the language 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 |
| 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 |
Anyone can check this report against the authoritative record — click the stamp, or enter ZKFP-QP79-PCP0 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/ZKFPQP79PCP0?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: 60.0authenticated: False |
| 7.8s | cloned the repository to a temporary directory | depth: full |
| 15.7s | read the git history | commits: 5362tracked files: 5334 |
| 158.7s | ran the deterministic checks | blame pass: Falseread working tree: False |
| 158.7s | recorded where this scan ran | attested: Falseenvironment: cloud-run |
| 236.3s | kept the facts, never the source, for re-reading under new checks | |
| 236.3s | deleting the working copy |
Total 236.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).