Read 2026-10-23
cadence-workflow/cadence: technical due diligence, read from its repository
What Borehole read in cadence-workflow/cadence's code and history at 65a48aa: its licence, security advisories, releases, review practice, tests, dependencies and operations. Every finding cites the file and line it rests on. The full report also covers the team and asks the questions the code cannot answer.
| Dimension | Rating |
|---|---|
| Architecture & Codebase — including AI provenance | strong |
| Engineering Process & SDLC Maturity | strong |
| Product & Engineering Maturity | strong |
| Security & Reliability Posture | adequate |
| Observability & Operations | strong |
| Fit with the Acquirer | not assessable |
What the repository says
CONTRIBUTING.md:12: names CNCF.gitmodules:1: 1 submodule(s) this survey does not read: idls
Architecture & Codebase — including AI provenance
strongcommon/types/shared.go is 10,083 lines, 59× this codebase's median file
adequateThe median source file here is 169 lines. 23 files exceed 1,690 lines, the largest being 10,083. 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.
common/types/shared.go:1 — 10,083 lines (59× median) |
common/types/mapper/thrift/shared.go:1 — 9,212 lines (54× median) |
common/types/mapper/proto/api.go:1 — 7,075 lines (41× median) |
common/dynamicconfig/dynamicproperties/constants.go:1 — 6,408 lines (37× median) |
common/persistence/sql/sqlplugin/interface_mock.go:1 — 5,876 lines (34× median) |
Engineering Process & SDLC Maturity
strongNo finding.
Product & Engineering Maturity
strong5 files still carry code deprecated more than two years ago
adequate5 files were marked deprecated over two years ago and still are, the oldest since Jan 2020. A deprecation is a promise to remove. Ask what still depends on these, and whether removing them is scheduled.
common/archiver/gcloud/connector/clientDelegate.go — deprecated since Jan 2020 |
.gen/proto/matching/v1/service.pb.go — deprecated since Jan 2021 |
common/config/config.go — deprecated since May 2021 |
common/config/cluster.go — deprecated since Aug 2021 |
common/persistence/data_manager_interfaces.go — deprecated since Jun 2024 |
Security & Reliability Posture
adequate6 credential-shaped strings in the tree sit in tests, examples, documentation or local development settings
adequateStrings shaped like credentials appear only where fakes are usual: test fixtures, examples, documentation, placeholders and local stacks. They are almost always fakes. Ask someone to confirm that none of them works anywhere, because a real key in a development file is still a real key.
| 5 cited: JWT, where fakes are usual |
1 Dockerfile runs 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.
docker/github_actions/Dockerfile — runs as root |
The build runs third-party code it does not pin
adequate7 third-party CI actions are referenced by a tag or branch rather than a commit, so they run whatever that tag points to on the day. Tags have been moved to malicious commits in real supply-chain attacks, and a piped script is whatever the server returns that minute. Pinning to a commit is the fix, and it is small.
.github/workflows/ci-checks.yml:38 — action pinned by tag |
.github/workflows/codecov-on-master.yml:39 — action pinned by tag |
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.
common/persistence/nosql/nosqlplugin/cassandra/setup.go:52 — SQL built from a string |
1 locked dependency has published vulnerabilities
adequate1 of 190 locked dependencies match 1 published advisories in OSV. 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.
cmd/server/go.mod — go.opentelemetry.io/otel/sdk v1.44.0: GHSA-8wmf-6v46-5gfg (low), fixed in 1.45.0 |
Observability & Operations
strongNo 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.
| no error reporter initialised |
7 of 26 deployed images carry no version, or `latest`
adequate7 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.
docker/github_actions/docker-compose-pinot.yml:19 — image without a version |
docker/docker-compose.yml:23 — image without a version |
docker/github_actions/docker-compose-local-replication-simulation.yml:134 — image without a version |
Fit with the Acquirer
not assessableNot rated: structurally not assessable from a repository.
Read more, or read your own
The full report on cadence-workflow/cadence: every dimension, the questions for the room, and the audit log.
Survey a repository: free on public repositories. Private code is read on your own machine by a collector whose source you can read first.