Read 2026-10-28
datalens-tech/datalens: technical due diligence, read from its repository
What Borehole read in datalens-tech/datalens's code and history at 1cebb39: 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 | not assessable |
| Security & Reliability Posture | strong |
| Observability & Operations | adequate |
| Fit with the Acquirer | not assessable |
Architecture & Codebase — including AI provenance
stronginit.sh is 1,088 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,088. 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.
init.sh:1 — 1,088 lines (15× median) |
Engineering Process & SDLC Maturity
adequateTests are absent or token
adequate0 test files against 20 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 / 20 source files |
Pinned dependencies have not moved in 16 months
adequateThe lockfile last changed 501 days before the newest commit, and 86 commits have landed since. Every security fix published upstream in that time is absent until someone updates it, and the longer the gap the larger and riskier that update becomes.
| .github/workflows/scripts/changelog/uv.lock last changed 2025-04-10 |
Product & Engineering Maturity
not assessableEffort is shifting from building to rewriting
adequateDeleted lines per line added rose from 0.02 to 1.03 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.02, second half 1.03 (split 2025-03-09) |
Security & Reliability Posture
strongNo finding.
Observability & Operations
adequateNo telemetry or error reporting is wired in anywhere
adequateNone of 90 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 90 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 |
2 of 9 deployments run a single replica
adequate2 deployments set `replicas: 1`, and nothing (an autoscaler, a disruption budget) adds more. Every deploy and every node drain is downtime, and the availability the buyer inherits has a ceiling.
helm/templates/deployment-postgres.yaml — replicas: 1 |
helm/templates/deployment-temporal.yaml — replicas: 1 |
Fit with the Acquirer
not assessableNot rated: structurally not assessable from a repository.
Read more, or read your own
The full report on datalens-tech/datalens: 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.