Read 2026-10-23
e-m-b-a/emba: technical due diligence, read from its repository
What Borehole read in e-m-b-a/emba's code and history at 153c7ff: 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 | adequate |
| Engineering Process & SDLC Maturity | adequate |
| Product & Engineering Maturity | adequate |
| Security & Reliability Posture | adequate |
| Observability & Operations | adequate |
| Fit with the Acquirer | not assessable |
Architecture & Codebase — including AI provenance
adequateCommit messages are templated rather than written
adequate43% of commit subjects are exact repeats of another subject, and subject length varies by only 13.4 characters. A log written by someone explaining their reasoning to a future reader does not look like this. The log is therefore weak evidence of intent, whatever the code is like.
| 192× 'cleanup' |
| 187× 'Update Snyk database' |
| 177× 'Update CISA known exploited vulnerability database' |
modules/S99_grepit.sh is 6,133 lines, 63× this codebase's median file
adequateThe median source file here is 97 lines. 7 files exceed 1,000 lines, the largest being 6,133. 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.
modules/S99_grepit.sh:1 — 6,133 lines (63× median) |
modules/L10_system_emulation.sh:1 — 3,222 lines (33× median) |
modules/F50_base_aggregator.sh:1 — 1,194 lines (12× median) |
helpers/helpers_emba_prepare.sh:1 — 1,063 lines (10× median) |
modules/S115_usermode_emulator.sh:1 — 1,061 lines (10× median) |
1 base image floats: no version, or `latest`
adequate1 of 1 `FROM` lines in product Dockerfiles name an image without a version, or with `latest`. Each build pulls whatever the registry serves that day, so the image that ships can change without a commit, and last month's build cannot be reproduced. Pin a version, or a digest.
Dockerfile:1 — base image without a version |
Engineering Process & SDLC Maturity
adequateTests cover a thin slice of the codebase
adequate25 test files against 293 source files (8.5%). 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.
| 25 test files / 293 source files |
26% of commit subjects say nothing about the change
adequate1,546 of 5,962 subjects are either under twelve characters or one of the standard placeholders — wip, fix, update. The history is therefore not usable for reconstructing why a decision was taken, which is the main thing an inheriting engineer needs it for. It says nothing about code quality and a great deal about how much context transfers with the asset.
| 1,546/5,962 low-content subjects (25.9%) |
| 'small fixes' |
| 'cleanup' |
| 'README fix' |
| 'print fix' |
Product & Engineering Maturity
adequate2% of bug fixes add or change a test
adequateOf 218 fixes in the last 24 months, 5 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.
| 5 of 218 |
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 |
The build runs third-party code it does not pin
adequate1 third-party CI action is referenced by a tag or branch rather than a commit, so they run whatever that tag points to on the day; 1 step pipes 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.
.github/workflows/codacy.yml:45 — action pinned by tag |
installer/I01_default_apps.sh:128 — download piped into a shell |
2 workload settings can give a container the host, behind a chart value or in a stack built from source
adequate2 places run a container privileged or in the host's namespaces only when a Helm value switches them on, or in a compose file that builds the product from this repository, which is how it is developed rather than how it ships. Neither is on by default in what ships. Ask whether production sets the value or runs that stack.
docker-compose.yml:9 — host access behind a setting or in a local stack |
docker-compose.yml:77 — host access behind a setting or in a local stack |
Observability & Operations
adequateNo telemetry or error reporting is wired in anywhere
adequateNone of 935 readable files references an instrumentation, metrics or error-reporting library. If this system is in production, nobody learns that it broke from the system itself — they learn it from a customer. That is a reliability finding before it is an observability one.
| searched 935 tracked text files for 16 known instrumentation libraries; manifests for metrics, tracing and error-reporting families; locked dependencies for the packages that emit; 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 |
Fit with the Acquirer
not assessableNot rated: structurally not assessable from a repository.
Read more, or read your own
The full report on e-m-b-a/emba: 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.