Read 2026-11-03
instill-ai/instill-core: technical due diligence, read from its repository
What Borehole read in instill-ai/instill-core's code and history at b9976c4: 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 | adequate |
| Security & Reliability Posture | adequate |
| Observability & Operations | adequate |
| Fit with the Acquirer | not assessable |
What the repository says
LICENSE: Relicensed: Apache-2.0 → Elastic-2.0 (2023-05-29)
Architecture & Codebase — including AI provenance
strongNo finding.
Engineering Process & SDLC Maturity
strongNo finding.
Product & Engineering Maturity
adequateChange keeps returning to the same few files
adequateFive files out of 683 absorb 25% of all file-level change. Concentration like this is where debt is usually being serviced rather than repaid: the same code is reopened because it is load-bearing, fragile, or both. A repository cannot tell you which — that is a conversation with the team.
.env — 234 commits touched it |
docker-compose.yml — 181 commits touched it |
Makefile — 157 commits touched it |
charts/core/values.yaml — 131 commits touched it |
README.md — 90 commits touched it |
Effort is shifting from building to rewriting
adequateDeleted lines per line added rose from 0.71 to 19.00 between the first and second halves of this history. Rework is normal and often healthy, but a rising ratio means an increasing share of the team's time is spent replacing code that already exists rather than building what does not. Whether that is deliberate repayment or churn is a question for the team.
| first half 0.71, second half 19.00 (split 2024-03-21) |
2% of bug fixes add or change a test
adequateOf 46 fixes in the last 24 months, 1 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.
| 1 of 46 |
Security & Reliability Posture
adequate1 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.
Dockerfile — runs as root |
4 environment files are committed
adequate.env, .env.secrets.component, .env.secrets.component.test 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.
.env — committed environment file |
.env.secrets.component — committed environment file |
.env.secrets.component.test — committed environment file |
The build runs third-party code it does not pin
adequate8 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/add-comment-to-issue.yml:14 — action pinned by tag |
.github/workflows/integration-test.yml:18 — action pinned by tag |
3 workload settings give a container the host
adequate3 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.
charts/core/templates/pipeline-backend/deployment.yaml:118 — privileged or host namespace |
configs/helm/ray/manifests/raycluster.yaml:45 — privileged or host namespace |
configs/helm/ray/manifests/raycluster.yaml:86 — privileged or host namespace |
Licence text does not match a standard licence
adequateLICENSE exists but its text does not match any standard licence. A bespoke or hand-edited licence is not wrong, but it cannot be cleared by recognising its name: counsel has to read it, and until they do neither side knows precisely what rights transfer with the code.
LICENSE:1 — 120 lines, unrecognised |
Relicensed: Apache-2.0 → Elastic-2.0 (2023-05-29)
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.
Observability & Operations
adequateNo 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.
| searched 158 files for 10 structured logging libraries; 0 matched |
One request cannot be followed through the logs
adequateNothing in the service carries a request or correlation id, and there is no tracing. When a customer reports a failure, the log lines that belong to their request cannot be picked out from everyone else's.
| no request id, correlation id or tracing found |
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.
| no error reporter initialised |
1 of 11 deployed images carry no version, or `latest`
adequate1 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.
charts/core/templates/registry/maintenance.yaml:57 — image without a version |
Readiness and liveness probes are identical in 3 of 9 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.
charts/core/templates/api-gateway/deployment.yaml — same probe endpoint twice |
charts/core/templates/console/deployment.yaml — same probe endpoint twice |
charts/core/templates/registry/deployment.yaml — same probe endpoint twice |
Fit with the Acquirer
not assessableNot rated: structurally not assessable from a repository.
Read more, or read your own
The full report on instill-ai/instill-core: 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.