Read 2026-10-28
oomol-lab/open-connector: technical due diligence, read from its repository
What Borehole read in oomol-lab/open-connector's code and history at fa58885: 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 | adequate |
| Product & Engineering Maturity | strong |
| Security & Reliability Posture | adequate |
| Observability & Operations | adequate |
| Fit with the Acquirer | not assessable |
What the repository says
LICENSE.txt:1: The licence is Apache-2.0 with a commercial-licence condition: source available, not open sourceLICENSE.txt: Relicensed: Apache-2.0 → Apache-2.0 with a commercial-licence condition (2026-10-27)
Architecture & Codebase — including AI provenance
strongsrc/providers/postman/generated.ts is 10,572 lines, 84× this codebase's median file
adequateThe median source file here is 125 lines. 81 files exceed 1,250 lines, the largest being 10,572. 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.
src/providers/postman/generated.ts:1 — 10,572 lines (84× median) |
src/providers/googledrive/actions.ts:1 — 7,483 lines (59× median) |
src/providers/vaquill/schemas.ts:1 — 5,504 lines (44× median) |
src/providers/investoday_mcp/official-tools/stocks.ts:1 — 5,111 lines (40× median) |
src/providers/contextdev/input-schemas.ts:1 — 4,108 lines (32× median) |
Engineering Process & SDLC Maturity
adequateTests cover a thin slice of the codebase
adequate294 test files against 7,415 source files (4.0%). This does not measure whether the tests are good, only whether enough of them exist for the codebase to be changed safely by someone who did not write it — which is exactly the situation after an acquisition.
| 294 test files / 7,415 source files |
18% of recent commits change more than 2,000 lines
adequate152 of 823 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.
| 152 commits over 2,000 lines |
Product & Engineering Maturity
strongNo finding.
Security & Reliability Posture
adequate27 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: Slack token, 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/Dockerfile — runs as root |
The build runs third-party code it does not pin
adequate4 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/publish-docker.yml:70 — action pinned by tag |
.github/workflows/publish-docker.yml:78 — 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. 1 of them put a value into the string; in the rest, what the code shows going in is a table or column name, a constant, or something the line does not show. Ask whether any value reaches these strings, rather than a parameter.
src/server/storage/postgres/runtime-store.ts:371 — SQL built from a string |
2 locked dependencies have published vulnerabilities
adequate2 of 520 locked dependencies match 4 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.
package-lock.json — nodemailer 10.1.0: GHSA-85x2-q946-cp5h (moderate), fixed in 10.1.4 |
package-lock.json — qs 6.16.0: GHSA-6pq8-jhm2-2vcw (moderate), fixed in 6.16.1 |
The licence is Apache-2.0 with a commercial-licence condition: source available, not open source
adequateLICENSE.txt grants Apache-2.0 with a commercial-licence condition: source available, not open source; some uses need a commercial licence from the licensor. The reading comes from the licence's own title and clauses. Whether the terms fit the buyer's intended use, and whether any paid licence transfers with the code, is a question for counsel and the licensor.
LICENSE.txt:1 — 36 lines, Apache-2.0 AND LicenseRef-Terms-CommercialLicence |
Relicensed: Apache-2.0 → Apache-2.0 with a commercial-licence condition (2026-10-27)
adequateThe root licence changed 1 time(s). The latest terms restrict what users, hosts or a buyer may do in ways the earlier ones did not. Code taken under the old terms stays under them, so both matter in diligence.
LICENSE.txt — Apache-2.0 from 2026-06-30 |
LICENSE.txt — Apache-2.0 with a commercial-licence condition from 2026-10-27 |
Observability & Operations
adequateReadiness and liveness probes are identical in 1 of 1 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.
deploy/helm/open-connector/templates/deployment.yaml — same probe endpoint twice |
The code branches on the environment's name at 12 places
adequate12 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.
src/providers/check/executors.ts:144 — branch on the environment name |
src/providers/check/executors.ts:272 — branch on the environment name |
src/providers/check/executors.ts:277 — branch on the environment name |
Fit with the Acquirer
not assessableNot rated: structurally not assessable from a repository.
Read more, or read your own
The full report on oomol-lab/open-connector: 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.