fefb05f · 392 commits · 15,305 files
Issued 2026-10-23
Nothing significant. Questions worth asking about Security & Reliability Posture, Observability & Operations.
104 checks ran across 6 assessable dimensions. 3 findings are worth checking first. 20 findings, each with evidence. One dimension cannot be assessed without an acquirer.
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.
| Dimension | Rating | ||
|---|---|---|---|
| 01 | Architecture & Codebase — including AI provenance | adequate | |
| 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 |
- 6% 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 · adequate · ratings ↑The repository begins with most of itself already written
adequate worth checking firstThe first commit carries 1,923,430 lines — 85% of every line ever added. Whatever happened before that commit happened somewhere this repository cannot show you, so the early history is not available as evidence of how the system was designed.
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. If it holds when someone checks it, this finding is significant.
| 8901533 | 2025-07-20T09:36:12+00:00; +1,923,430 across 14811 files; subject: "feat: manually mirror opencoze's code from bytedance" |
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.
backend/api/model/plugin_develop/plugin_develop.go is 34,323 lines, 624× this codebase's median file
adequateThe median source file here is 55 lines. 125 files exceed 1,000 lines, the largest being 34,323. 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 98% 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 | backend/api/model/plugin_develop/plugin_develop.go:1 — 34,323 lines (624× median) |
| line-count | backend/api/model/data/database/table/table.go:1 — 33,404 lines (607× median) |
| line-count | backend/api/model/marketplace/product_public_api/public_api.go:1 — 33,324 lines (605× median) |
| line-count | backend/api/model/app/bot_common/bot_common.go:1 — 32,074 lines (583× median) |
| line-count | backend/api/model/workflow/workflow_svc.go:1 — 17,329 lines (315× 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 ↑7% of recent commits change more than 2,000 lines
adequate26 of 367 commits in the last 24 months changed over 2,000 lines of code, not counting reformatting, renames, vendored or generated code. A change that size is rarely reviewed line by line. Ask how they were reviewed, and what made them that large.
| git log --numstat | 26 commits over 2,000 lines |
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 ↑81 direct dependencies in a single manifest
adequatefrontend/packages/agent-ide/space-bot/package.json declares 81 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 | frontend/packages/agent-ide/space-bot/package.json — 81 declared |
| direct-dependencies | backend/go.mod — 77 declared |
| direct-dependencies | frontend/packages/agent-ide/bot-plugin/entry/package.json — 56 declared |
| direct-dependencies | frontend/packages/agent-ide/entry/package.json — 51 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.
18% of bug fixes add or change a test
adequateOf 193 fixes in the last 24 months, 35 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 | 35 of 193 |
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 jobs are each done by more than one library
adequateWithin a single package: CSS-in-JS: emotion, styled-components; dates: date-fns, dayjs. Each duplicate is bundle size, two ways of doing the same thing in one codebase, and two upgrade paths to maintain. It is usually the residue of a migration that stopped halfway.
| common/_templates/rsbuild-web/package.json | common/_templates/rsbuild-web/package.json — several libraries per job |
| common/_templates/rspack-web/package.json | common/_templates/rspack-web/package.json — several libraries per job |
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.
Go 1.24 is past end of life
adequateThe code is pinned to Go 1.24 (end of life 2026-02-10). None of these receives security fixes any more; the first stopped on 2026-02-10. Moving off an unsupported runtime is rarely a one-line change, so a buyer should ask whether the upgrade is planned and what it touches.
A note that does not affect this rating: in Borehole's calibration, this check's notes were usually true but overstated.
| backend/Dockerfile | backend/Dockerfile — Go 1.24, end of life 2026-02-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.
Security & Reliability Posture
05 · adequate · ratings ↑2 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 | backend/Dockerfile — runs as root |
| no-USER-instruction | frontend/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.
110 locked dependencies have published vulnerabilities, 62 high or critical in what ships
adequate worth checking first110 of 4,564 locked dependencies match 192 published advisories in OSV, 98 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. This lockfile pins development tools alongside what ships and does not say which is which, so some of these may never reach a user.
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 backend/go.mod and the 2 other files it cites settles it. If it holds when someone checks it, this finding is significant.
| backend/go.mod | backend/go.mod — golang.org/x/crypto v0.39.0: GHSA-5cgq-3rg8-m6cv (critical), fixed in 0.52.0 |
| common/autoinstallers/plugins/pnpm-lock.yaml | common/autoinstallers/plugins/pnpm-lock.yaml — handlebars 4.7.8: GHSA-2w6w-674q-4c4q (critical), fixed in 4.7.9 |
| common/config/subspaces/default/pnpm-lock.yaml | common/config/subspaces/default/pnpm-lock.yaml — jsrsasign 10.9.0: GHSA-5jx8-q4cp-rhh6 (critical), fixed in 11.1.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.
5 workload settings give a container the host
adequate worth checking first5 places in the deployment configuration run a container privileged or in the host's network, process or IPC namespace. A compromise of that container is a compromise of the machine, and most acquirers' security reviews block it. Node agents (network, storage, monitoring) are excluded.
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 docker/docker-compose-oceanbase.yml:45 settles it. If it holds when someone checks it, this finding is significant.
| docker/docker-compose-oceanbase.yml | docker/docker-compose-oceanbase.yml:45 — privileged or host namespace |
| docker/docker-compose-oceanbase.yml | docker/docker-compose-oceanbase.yml:77 — privileged or host namespace |
| docker/docker-compose-oceanbase.yml | docker/docker-compose-oceanbase.yml:162 — privileged or host namespace |
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; 4 steps pipe 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/ci.yml | .github/workflows/ci.yml:39 — action pinned by tag |
| .github/workflows/ci.yml | .github/workflows/ci.yml:172 — action pinned by tag |
| scripts/setup/db_migrate_apply.sh | scripts/setup/db_migrate_apply.sh:37 — 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.
4 outbound calls can wait forever
adequate4 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.
| backend/domain/knowledge/service/knowledge.go | backend/domain/knowledge/service/knowledge.go:1126 — outbound call without a timeout |
| backend/infra/document/ocr/impl/impl.go | backend/infra/document/ocr/impl/impl.go:46 — outbound call without a timeout |
| backend/infra/document/parser/impl/impl.go | backend/infra/document/parser/impl/impl.go:43 — 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.
1 SQL statement built from strings
adequate1 places in product code build SQL by formatting or joining strings rather than passing parameters. In each, what the code shows going in is a table or column name, a constant, or something the line does not show, not a request's value. 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/infra/oceanbase/oceanbase_official.go | backend/infra/oceanbase/oceanbase_official.go:86 — 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.
11 places insert HTML from a variable without sanitising it
adequate11 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.
| backend/conf/admin/index.html | backend/conf/admin/index.html:933 — HTML from a variable |
| backend/conf/admin/index.html | backend/conf/admin/index.html:1279 — HTML from a variable |
| backend/conf/admin/index.html | backend/conf/admin/index.html:2109 — 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.
4 advisories against this project in the last 24 months, 4 high or critical
adequateThe newest was published on 2026-10-20. 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 3 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.5.1. 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.
| CVE-2026-77934 | 2026-10-20: CVE-2026-77934 (high): Coze Studio before 0.5.0 contains an insecure default configuration that allows any registered user to execute commands by running workflow code nodes in an uns |
| CVE-2026-77935 | 2026-10-20: CVE-2026-77935 (high): Coze Studio through 0.5.1 contains an insecure direct object reference vulnerability in workflow.go that allows authenticated users to access other spaces' work |
| CVE-2026-92788 | 2026-09-16: CVE-2026-92788 (high): Coze Studio through 0.5.1 fails to validate that table names in workflow SQL customization nodes belong to the caller's workspace. Authenticated attackers can e |
| CVE-2026-92795 | 2026-09-16: CVE-2026-92795 (high): Coze Studio through 0.5.1 fails to restrict the server URL supplied when registering plugin tools, allowing authenticated users to make the backend fetch intern |
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 ↑Readiness and liveness probes are identical in 2 of 3 workloads
adequateBoth probes call the same endpoint. When a dependency slows down, the liveness probe fails with the readiness probe, so the platform restarts pods that only needed taking out of rotation, and a partial outage becomes a full one. Liveness should ask whether the process is alive; readiness whether it can serve.
| helm/charts/opencoze/templates/coze-web-deployment.yaml | helm/charts/opencoze/templates/coze-web-deployment.yaml — same probe endpoint twice |
| helm/charts/opencoze/templates/milvus-statefulset.yaml | helm/charts/opencoze/templates/milvus-statefulset.yaml — same probe endpoint twice |
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 error reporter is wired in
adequateNothing in the service initialises an error reporter (Sentry, Rollbar, Bugsnag, Honeybadger or an APM agent). An exception in production reaches a person only if someone is reading the logs, which usually means a customer reports it first.
A note that does not affect this rating: notes like it are common in well-run projects.
| error reporting | no error reporter initialised |
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 of 16 deployed images carry no version, or `latest`
adequate4 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/docker-compose-oceanbase_debug.yml | docker/docker-compose-oceanbase_debug.yml:341 — image without a version |
| docker/docker-compose-oceanbase.yml | docker/docker-compose-oceanbase.yml:333 — image without a version |
| docker/docker-compose-oceanbase.yml | docker/docker-compose-oceanbase.yml:364 — 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.
8 of 10 deployments run a single replica
adequate8 deployments set `replicas: 1`, and nothing (an autoscaler, a disruption budget) adds more. Every deploy and every node drain is downtime, and the availability the buyer inherits has a ceiling.
A note that does not affect this rating: in Borehole's calibration, this check's notes were usually true but overstated.
| helm/charts/opencoze/templates/elasticsearch-statefulset.yaml | helm/charts/opencoze/templates/elasticsearch-statefulset.yaml — replicas: 1 |
| helm/charts/opencoze/templates/etcd-statefulset.yaml | helm/charts/opencoze/templates/etcd-statefulset.yaml — replicas: 1 |
| helm/charts/opencoze/templates/milvus-statefulset.yaml | helm/charts/opencoze/templates/milvus-statefulset.yaml — replicas: 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.
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.
| frontend/packages/agent-ide/bot-plugin/entry/src/util/get-env.ts | frontend/packages/agent-ide/bot-plugin/entry/src/util/get-env.ts:18 — branch on the environment name |
| frontend/packages/agent-ide/bot-plugin/export/src/component/file-import/const.ts | frontend/packages/agent-ide/bot-plugin/export/src/component/file-import/const.ts:18 — branch on the environment name |
| frontend/packages/arch/bot-env-adapter/src/base.ts | frontend/packages/arch/bot-env-adapter/src/base.ts:41 — 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
11 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 10,900 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 62 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- 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 No threat model is in the tree of what looks like a running service. Does one exist elsewhere, and who owns it?
- measured Infrastructure code (helm/charts/opencoze/Chart.yaml) last changed 12 months before the newest commit, while 390 commits landed. Is the infrastructure now changed by hand? Compare the live account with the code.
- 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. Does your engineering organisation already run TypeScript in production, or would this be the first?
- The bulk of this system sits in frontend/, backend/, common/. Which of your existing systems would each of those have to absorb or replace?
- The repository carries deployment configuration (backend/Dockerfile and 51 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/coze-dev/coze-studio/fefb05f)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 — 84 signals that ran and did not fire
Appendix: rejection log — 84 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 — 69
| Signal | What it found |
|---|---|
| 04.hotspot_concentration | change is spread across the codebase rather than pooling in a few filesfiles 16,042 · top5 share 0.005 |
| 04.debt_markers | debt markers are sparsemarkers 351 · per kloc 0.2 · lines read 1,779,231 |
| 04.test_growth | test effort kept pace with code writtenlate test per code 0.204 · early test per code 0.098 |
| 04.churn_trend | rework is not rising against new worklate delete per insert 0.183 · early delete per insert 0.097 |
| 04.compat_layers | little code is kept for the old wayshare 0.001 · code files 7,567 · compat files 7 |
| 06.telemetry_presence | a telemetry or error-reporting library is referencednote presence only; whether anyone watches it is not visible here · matches 4 |
| 06.structured_logging | a structured logging library is referencedmatches 1 |
| 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 63 |
| 06.usage_reporting_default | the product's code names no reporting hostsettings on 1 · settings off 0 |
| 06.release_markers | releases are markedtags last year 11 · release commits 0 · changelog commits 1 |
| 06.migrate_on_start | migrations do not run at container start |
| 03.contributor_concentration | no single contributor dominates the last 24 monthsyears 1.0 · window last 24 months · authors 62 |
| 03.active_contributors | more than one contributor active in the trailing yearall time 62 · active 12mo 14 |
| 03.knowledge_silos | every substantial directory has been touched by more than one personauthors 62 · directories 7 |
| 03.drive_by_contributors | an open contributor base, where one-commit contributors are normalauthors 62 · one off share 0.548 |
| 03.contributor_attrition | the dominant contributor is still activeauthors 62 · 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 62 |
| 03.second_contributor_attrition | the second and third contributors are still active |
| 03.joiners_and_leavers | the team is not shrinkingleft 0 · joined 8 · regular last year 14 |
| 02.merge_discipline | a meaningful share of recent change carries evidence of reviewmerges 1 · 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 1,511 · source 8,974 · test ratio 0.168 |
| 02.release_cadence | tags are presenttags 13 |
| 02.conventional_commits | commit subjects generally carry contentsampled 391 · low content share 0.003 |
| 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 1,938 |
| 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.0 · reverts 0 · recent commits 391 |
| 02.dependency_update_cadence | dependencies move with the codelockfiles 9 · commits since 1 · days since lockfile changed 99 |
| 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 268 · ci configs 8 · product files 7,567 |
| 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.message_uniformity | commit subjects vary in wording and lengthlength stdev 21.55 · repeat share 0.005 |
| 01.revision_depth | most files were revisited after they were first writtenfiles seen 10,618 · write once share 0.405 |
| 01.swallowed_errors | errors are rarely thrown awayloc 1,792,114 · files 3 · per kloc 0.0 |
| 01.build_reproducibility | every base image names a versionfloating 0 · from lines 4 |
| 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 paths; the only other matches are expired or licence tokens or placeholders, which grant nothingnote the working tree only; the history is 05.5 · patterns 8 · files read 13,024 |
| 05.security_guardrails | at least one standard guard rail is configured |
| 05.dependency_pinning | a lockfile is committed, so builds are reproduciblelockfile True |
| 05.secrets_in_history | no credential-shaped string was ever added outside test and fixture paths; the only other matches are expired or licence tokens or placeholders, which grant nothingpatterns 8 · truncated False · added lines 2,057,672 |
| 05.secrets_management_pattern | no environment file is committed outside tests and examplesenv files 0 |
| 05.shell_from_strings | product code does not build shell commands from stringssites 0 |
| 05.unsafe_deserialization | no code-executing deserialiser in product codesites 0 |
| 05.tls_verification_off | no TLS verification is switched off in product codefiles 0 · sites 0 · pinned instead 0 |
| 05.resource_limits | every workload declares limitsworkloads 10 · without limits 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 | the newer API version is recent; the old one may be on its way outmonths together 12 |
| 04.deprecations_lingering | few deprecations have outlived two yearsolder than two years 0 · files with deprecations 83 |
| 04.dependency_churn | few dependencies were added and dropped within 60 daysdependencies seen 374 · added in two years 374 · removed within 60 days 6 |
| 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 0 · 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.5 · days since last tag 276 · commits last 90 days 1 |
| 04.release_branch | the newest release was cut from the branch surveyedelsewhere 3 · on branch 10 · tags in window 13 |
| 03.single_maintainer | no file says one person maintains itstatements 0 |
| 05.project_exploited | no affecting advisory is on CISA's Known Exploited listexploited 0 |
Could not conclude, or did not apply — 15
Not a clean result. Each says why it could not answer here.
| Signal | Why |
|---|---|
| 04.fix_share_trend | fewer than six busy quarters to compare |
| 04.schema_churn | no schema migrations to read |
| 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.feature_flags | no feature-flag service; flags may live elsewhere |
| 03.bus_factor_trend | fewer than three active years to compare |
| 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.migration_reversibility | too few migrations to judge |
| 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 |
| 05.project_advisories | could not tell whether 3 published advisories affect the surveyed code: its version could not be placed |
Anyone can check this report against the authoritative record — click the stamp, or enter GDZA-H3XD-QFHM 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/GDZAH3XDQFHM?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: 73.7authenticated: False |
| 5.7s | cloned the repository to a temporary directory | depth: full |
| 8.3s | read the git history | commits: 392tracked files: 15305 |
| 291.0s | ran the deterministic checks | blame pass: Falseread working tree: False |
| 291.1s | recorded where this scan ran | attested: Falseenvironment: cloud-run |
| 487.2s | kept the facts, never the source, for re-reading under new checks | |
| 487.2s | deleting the working copy |
Total 487.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).