Read 2026-11-03
topiam/eiam: technical due diligence, read from its repository
What Borehole read in topiam/eiam's code and history at ca2be26: 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 |
Architecture & Codebase — including AI provenance
strongCommit messages are templated rather than written
adequate74% of commit subjects are exact repeats of another subject, and subject length varies by only 9.2 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.
| 78× ':zap: 优化代码' |
| 58× ':zap: 优化' |
| 41× ':arrow_up: 依赖升级' |
eiam-common/src/main/java/cn/topiam/employee/common/enums/Country.java is 1,062 lines, 15× this codebase's median file
adequateThe median source file here is 69 lines. 1 file exceed 1,000 lines, the largest being 1,062. 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.
eiam-common/src/main/java/cn/topiam/employee/common/enums/Country.java:1 — 1,062 lines (15× median) |
Engineering Process & SDLC Maturity
adequateTests are absent or token
adequate0 test files against 1,565 source files (0.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.
| 0 test files / 1,565 source files |
52% of commit subjects say nothing about the change
adequate276 of 530 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.
| 276/530 low-content subjects (52.1%) |
| ':tada: 重磅发布' |
| ':zap: 优化代码' |
| ':memo: 优化文档' |
| ':zap: 兼容性调整' |
Almost no process scaffolding exists in the repository
adequateOf five ordinary markers — CI workflows, CODEOWNERS, a pull-request template, pre-commit hooks, contribution guidance — none are present. Branch protection itself is a GitHub setting rather than a file, so this is a reading of proxies and not of the rules themselves. What it does establish is that the process is not written down anywhere a new engineer would find it.
| 0 of 5 markers present across 1,691 tracked files |
Product & Engineering Maturity
strongNo finding.
Security & Reliability Posture
adequateNone of the standard security guard rails are configured
adequateThere is no disclosure policy, no automated dependency updates, no named code owners and no pre-commit configuration. None of these is load-bearing on its own. Their collective absence says that security posture here is whatever the current team happens to remember to do, which is not a posture that survives the team changing.
| checked 5 kinds of guard rail across 1,691 tracked files; 0 present |
3 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.
eiam-console/Dockerfile — runs as root |
eiam-openapi/Dockerfile — runs as root |
eiam-portal/Dockerfile — runs as root |
67 locked dependencies have published vulnerabilities, 31 high or critical in what ships
adequate67 of 1,865 locked dependencies match 157 published advisories in OSV, 75 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.
eiam-console/src/main/console-fe/pnpm-lock.yaml — hull.js 1.0.6: GHSA-q849-wxrc-vqrp (critical), fixed in 1.0.10 |
eiam-console/src/main/console-fe/pnpm-lock.yaml — maplibre-gl 3.6.2: GHSA-jrc7-96c5-q579 (critical), fixed in 6.4.1 |
eiam-console/src/main/console-fe/pnpm-lock.yaml — form-data 4.0.2: GHSA-fjxv-7rqg-78g4 (critical), fixed in 4.0.4; a development dependency |
5 places insert HTML from a variable without sanitising it
adequate5 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.
eiam-console/src/main/console-fe/src/components/IconFont/lib/iconfont.js:46 — HTML from a variable |
eiam-console/src/main/console-fe/src/pages/account/IdentitySourceDetail/components/BasicConfig/index.tsx:76 — HTML from a variable |
eiam-console/src/main/console-fe/src/pages/authn/IdentityProvider/components/Config/CallbackUrl.tsx:39 — HTML from a variable |
Observability & Operations
adequateNo telemetry or error reporting is wired in anywhere
adequateNone of 1,640 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 1,640 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 |
No 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 1,640 files for 10 structured logging libraries; 0 matched |
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 topiam/eiam: 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.