e5cd869 · 2,977 commits · 2,741 files
Issued 2026-10-23
Nothing significant. Questions worth asking about Security & Reliability Posture, Observability & Operations.
103 checks ran across 6 assessable dimensions. 1 finding is worth checking first. 13 findings, each with evidence. One dimension cannot be assessed without an acquirer.
- 05.60 Relicensed: GPL-3.0 → MIT (2023-02-15) LICENSE
- 05.61 Part of the code is under a separate licence: ee/ ee/LICENSE
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 64 locked dependencies have published vulnerabilities, 53 high or critical in what ships
- 3 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 | strong | |
| 04 | Product & Engineering Maturity | adequate | |
| 05 | Security & Reliability Posture | adequate | |
| 06 | Observability & Operations | adequate | |
| 07 | Fit with the Acquirer | not assessable |
- 26% 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 ↑keep/api/core/db.py is 6,006 lines, 95× this codebase's median file
adequateThe median source file here is 63 lines. 15 files exceed 1,000 lines, the largest being 6,006. Size is not a defect on its own — some problems genuinely live in one place — but these are where merge conflicts, review fatigue and single-owner knowledge concentrate, and they are the first thing that slows an inheriting engineer down.
A note that does not affect this rating: measured against its own codebase's median, it is below the 85th percentile of 382 surveyed projects' largest files, where this check begins to count.
| line-count | keep/api/core/db.py:1 — 6,006 lines (95× median) |
| line-count | keep/providers/grafana_provider/grafana_provider.py:1 — 1,773 lines (28× median) |
| line-count | keep/providers/datadog_provider/datadog_provider.py:1 — 1,641 lines (26× median) |
| line-count | keep/cli/cli.py:1 — 1,601 lines (25× median) |
| line-count | keep/api/routes/alerts.py:1 — 1,518 lines (24× 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 · 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 ↑91 direct dependencies in a single manifest
adequatekeep-ui/package.json declares 91 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 | keep-ui/package.json — 91 declared |
| direct-dependencies | pyproject.toml — 89 declared |
| direct-dependencies | keep/providers/fluxcd_provider/requirements.txt — 2 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 ↑12 of 94 migrations cannot be rolled back
adequate12 schema migrations (13%) have no working way back: an empty `downgrade`, a `down` that does nothing, or a data migration with no reverse. A bad deploy that includes one is recovered from a backup, not reverted. Ask when a restore was last rehearsed.
| keep/api/models/db/migrations/versions/2024-10-29-18-37_991b30bcf0b9.py | keep/api/models/db/migrations/versions/2024-10-29-18-37_991b30bcf0b9.py:58 — migration with no way back |
| keep/api/models/db/migrations/versions/2025-01-19-10-44_d359baaf0836.py | keep/api/models/db/migrations/versions/2025-01-19-10-44_d359baaf0836.py:20 — migration with no way back |
| keep/api/models/db/migrations/versions/2025-02-05-15-46_e343054ae740.py | keep/api/models/db/migrations/versions/2025-02-05-15-46_e343054ae740.py:47 — migration with no way back |
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.
64 locked dependencies have published vulnerabilities, 53 high or critical in what ships
adequate worth checking first64 of 1,611 locked dependencies match 131 published advisories in OSV, 69 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 poetry.lock settles it. If it holds when someone checks it, this finding is significant.
| poetry.lock | poetry.lock — anyio 4.7.0: GHSA-82r6-8w77-94w6 (critical), fixed in 4.14.2 |
| poetry.lock | poetry.lock — certifi 2024.12.14: GHSA-6q48-6c7w-9gw2 (critical), fixed in 2026.10.19 |
| poetry.lock | poetry.lock — snowflake-connector-python 3.13.1: GHSA-5cc2-282f-jjq2 (critical), fixed in 3.18.1 |
Respond to this finding
Your response is published beside the finding, not instead of it. A finding you can argue with is the point — and a wrong one is calibration data we want.
An owner's response is removed only when it is unlawful, impersonates someone, publishes personal data or a credential, or is not about the finding. Disagreeing with the report is never a reason. To report a response, or to reach us about one, write to takedown@borehole.dev.
Part of the code is under a separate licence: ee/
adequateA directory named for a paid edition carries its own licence. That code is usually not open source even where the rest is; what the buyer may do with each part differs.
| ee/LICENSE | ee/LICENSE — licence: 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.
The build runs third-party code it does not pin
adequate15 third-party CI actions are referenced by a tag or branch rather than a commit, so they run whatever that tag points to on the day. Tags have been moved to malicious commits in real supply-chain attacks, and a piped script is whatever the server returns that minute. Pinning to a commit is the fix, and it is small.
A note that does not affect this rating: notes like it are common in well-run projects.
| .github/workflows/auto-release.yml | .github/workflows/auto-release.yml:45 — action pinned by tag |
| .github/workflows/auto-resolve-keep.yml | .github/workflows/auto-resolve-keep.yml:52 — 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.
171 outbound calls can wait forever
adequate171 HTTP calls use a client with no timeout (Python `requests` without `timeout=`, or Go's default client). When a dependency slows down, each one holds a worker until the connection gives up, and enough of them take the service down with the dependency.
A note that does not affect this rating: in Borehole's calibration, this check's notes were usually true but overstated.
| ee/identitymanager/identity_managers/azuread/azuread_authverifier.py | ee/identitymanager/identity_managers/azuread/azuread_authverifier.py:92 — outbound call without a timeout |
| keep/api/core/demo_mode.py | keep/api/core/demo_mode.py:213 — outbound call without a timeout |
| keep/api/core/demo_mode.py | keep/api/core/demo_mode.py:227 — outbound call without a timeout |
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.
3 shell commands built from strings
adequate3 places run a command through a shell (`shell=True`, `os.system`, `exec` with a template) rather than passing arguments. Where any part comes from outside, it is command injection. Ask where each one's input comes from.
A note that does not affect this rating: in Borehole's calibration, this check's notes were usually true but overstated.
| keep/providers/bash_provider/bash_provider.py | keep/providers/bash_provider/bash_provider.py:36 — command run through a shell |
| keep/providers/bash_provider/bash_provider.py | keep/providers/bash_provider/bash_provider.py:53 — command run through a shell |
| keep/providers/bash_provider/bash_provider.py | keep/providers/bash_provider/bash_provider.py:104 — command run through 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.
1 deserialiser that can run code
adequate1 places read data with a deserialiser that executes what it reads (`yaml.load` without a safe loader). That is safe on data the system wrote itself and remote code execution on anything else. Ask where each one's input comes from.
A note that does not affect this rating: in Borehole's calibration, this check's notes were usually true but overstated.
| keep/functions/cyaml.py | keep/functions/cyaml.py:57 — code-executing deserialiser |
Respond to this finding
Your response is published beside the finding, not instead of it. A finding you can argue with is the point — and a wrong one is calibration data we want.
An owner's response is removed only when it is unlawful, impersonates someone, publishes personal data or a credential, or is not about the finding. Disagreeing with the report is never a reason. To report a response, or to reach us about one, write to takedown@borehole.dev.
Relicensed: GPL-3.0 → MIT (2023-02-15)
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".
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-07-21. 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 1 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 0.54.3. Answer lives in: the release you run, set against each fixed version. The record is incomplete: NVD: 450 records name keep with nothing tying them to this repository (CVE-2006-6763, CVE-2006-6764, CVE-2008-1635, …).
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.
| CVE-2026-65057 | 2026-07-21: CVE-2026-65057 (critical): Keep (commit 91c75e0) contains a server-side request forgery vulnerability that allows unauthenticated attackers to make the backend issue arbitrary HTTP reques |
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 1,835 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.
23 of 43 deployed images carry no version, or `latest`
adequate23 images in the deployment configuration are named without a version or as `latest`. A redeploy can change the software without a commit, a rollback has nothing to roll back to, and nobody can say from the repository what is running.
A note that does not affect this rating: in Borehole's calibration, this check's notes were usually true but overstated.
| docker-compose.yml | docker-compose.yml:6 — image without a version |
| proxy/docker-compose-proxy.yml | proxy/docker-compose-proxy.yml:67 — image without a version |
| docker-compose-with-arq.yml | docker-compose-with-arq.yml:37 — image without a version |
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
5 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 No architecture or design document is in the tree, across 1,715 product files. Where does the design live, and who holds it?
- 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 202 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 161 commits landed in the last year, against 1,198 the year before (-87%). Is that maintenance mode, a pivot, or fewer people working on it? The count looks the same for all three.
- Can this team deliver the stated roadmap on the stated timeline?
- Does leadership know about the debt, and is time budgeted to repay it?
- Is the engineering shape consistent with the commercial story?
Security & Reliability Posture
05 · partial coverage- 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 Nothing in the tree backs up or restores data. How is data backed up, and has a restore ever been rehearsed?
- measured Alert rules are defined in the repository. 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 Python alongside (45% 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 keep-ui/, keep/, ee/. Which of your existing systems would each of those have to absorb or replace?
- The repository carries deployment configuration (docker-compose-with-arq.yml and 22 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/keephq/keep/e5cd869)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 — 90 signals that ran and did not fire
Appendix: rejection log — 90 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 — 72
| Signal | What it found |
|---|---|
| 04.hotspot_concentration | change is spread across the codebase rather than pooling in a few filesfiles 4,758 · top5 share 0.067 |
| 04.debt_markers | debt markers are sparsemarkers 192 · per kloc 0.76 · lines read 251,130 |
| 04.test_growth | test effort kept pace with code writtenlate test per code 0.365 · early test per code 0.078 |
| 04.churn_trend | rework is not rising against new worklate delete per insert 0.395 · early delete per insert 0.373 |
| 04.eol_runtime | every pinned runtime is still supportedeol as of 2026-09-24 |
| 04.fixes_with_tests | fixes usually come with a testfixes 893 · share 0.239 · with tests 213 |
| 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 1,364 · compat files 0 |
| 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 109 |
| 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 17 |
| 06.error_reporting | an error reporter is initialisedinitialised 3 · config files 4 |
| 06.usage_reporting_default | the product's code names no reporting hostsettings on 0 · settings off 0 |
| 06.alert_rules | alert rules are defined as codealert files 11 |
| 06.environment_branching | environment differences live in configurationsites 0 |
| 06.release_markers | releases are markedtags last year 13 · release commits 1 · changelog commits 0 |
| 06.migrate_on_start | migrations do not run at container start |
| 03.contributor_concentration | no single contributor dominates the last 24 monthsyears 3.7 · window last 24 months · authors 202 |
| 03.active_contributors | more than one contributor active in the trailing yearall time 202 · active 12mo 69 |
| 03.knowledge_silos | every substantial directory has been touched by more than one personauthors 202 · directories 5 |
| 03.drive_by_contributors | an open contributor base, where one-commit contributors are normalauthors 202 · one off share 0.599 |
| 03.contributor_attrition | the dominant contributor is still activeauthors 202 · top share a quarter or more · top contributor last committed within the last three months |
| 03.critical_path_ownership | more than one person changes the critical pathsauthors 128 |
| 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 13 · joined 14 · regular last year 16 |
| 02.merge_discipline | a meaningful share of recent change carries evidence of reviewmerges 0 · window last 24 months · with tracked 0 |
| 02.ci_presence | CI configuration is present in the working treecount 16 |
| 02.test_presence | tests are present in a normal proportion to sourcetests 162 · source 1,523 · test ratio 0.106 |
| 02.release_cadence | tags are presenttags 315 |
| 02.conventional_commits | commit subjects generally carry contentsampled 2,905 · low content share 0.015 |
| 02.branch_protection_hints | process scaffolding is present in the repository |
| 02.ci_runs_tests | CI invokes a test runnerconfigs 16 · with tests 5 |
| 02.skipped_tests | few tests are switched offfocused 0 · skipped 0 · test files 211 |
| 02.ci_test_gating | no test run in CI is written so that it cannot failconfigs 16 |
| 02.revert_share | change is rarely undoneshare 0.0 · reverts 0 · recent commits 1,361 |
| 02.dependency_update_cadence | dependencies move with the codelockfiles 3 · commits since 120 · days since lockfile changed 239 |
| 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 6 · ci configs 16 · product files 1,364 |
| 02.commit_size | changes arrive in reviewable sizesshare 0.02 · commits 1,296 · over 2000 lines 26 |
| 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 182 · share of insertions 0.0003 |
| 01.message_uniformity | commit subjects vary in wording and lengthlength stdev 18.82 · repeat share 0.002 |
| 01.revision_depth | most files were revisited after they were first writtenfiles seen 1,598 · write once share 0.434 |
| 01.duplicated_blocks | little shipping code is repeated verbatim across filesshare 0.0133 · product files 1,361 · distinct blocks 131,722 |
| 01.swallowed_errors | errors are rarely thrown awayloc 252,879 · files 35 · per kloc 0.19 |
| 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 1,835 |
| 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.secrets_management_pattern | no environment file is committed outside tests and examplesenv files 0 |
| 05.sql_from_strings | no SQL is assembled from strings in product codefiles 0 · sites 0 · value interpolated 0 |
| 05.privileged_workloads | no workload runs privileged or in the host's namespacessites 0 · behind a setting or built here 0 |
| 05.public_env_secret | only publishable values carry a public prefixnames 0 · sites 0 · not secrets 0 |
| 05.unsafe_html | raw HTML is rare, literal or sanitisedsites 1 |
| 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 MITclass permissive · license MIT |
| 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 3 |
| 04.dependency_churn | few dependencies were added and dropped within 60 daysdependencies seen 353 · added in two years 62 · removed within 60 days 2 |
| 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 |
| 04.releases_stopped | releases keep pace with developmentmedian gap days 17.5 · days since last tag 44 · commits last 90 days 33 |
| 04.release_branch | the newest release was cut from the branch surveyedelsewhere 2 · on branch 311 · tags in window 313 |
| 03.single_maintainer | no file says one person maintains itstatements 0 |
Could not conclude, or did not apply — 18
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.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.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.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 |
| 04.api_versions_coexisting | one API version is served, or none |
| 05.project_advisories | record incomplete: no advisory found in the sources that answered; NVD: 450 records name keep with nothing tying them to this repository (CVE-2006-6763, CVE-2006-6764, CVE-2008-1635, …) |
| 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 TKC5-5M97-DTED 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/TKC55M97DTED?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: 84.8authenticated: False |
| 6.3s | cloned the repository to a temporary directory | depth: full |
| 9.8s | read the git history | commits: 2977tracked files: 2741 |
| 96.0s | ran the deterministic checks | blame pass: Falseread working tree: False |
| 96.1s | recorded where this scan ran | attested: Falseenvironment: cloud-run |
| 137.2s | kept the facts, never the source, for re-reading under new checks | |
| 137.2s | deleting the working copy |
Total 137.2s ·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).