Read 2026-11-03
lmnr-ai/lmnr: technical due diligence, read from its repository
What Borehole read in lmnr-ai/lmnr's code and history at 99d1eae: 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 | adequate |
| Security & Reliability Posture | adequate |
| Observability & Operations | adequate |
| Fit with the Acquirer | not assessable |
Architecture & Codebase — including AI provenance
strongapp-server/src/traces/spans.rs is 5,245 lines, 76× this codebase's median file
adequateThe median source file here is 69 lines. 14 files exceed 1,000 lines, the largest being 5,245. 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.
app-server/src/traces/spans.rs:1 — 5,245 lines (76× median) |
app-server/src/main.rs:1 — 2,874 lines (41× median) |
app-server/src/query_engine/validator/tests.rs:1 — 2,621 lines (37× median) |
app-server/src/mq/stream/reader.rs:1 — 2,266 lines (32× median) |
app-server/src/query_engine/validator.rs:1 — 2,093 lines (30× median) |
Engineering Process & SDLC Maturity
adequateTests cover a thin slice of the codebase
adequate197 test files against 2,239 source files (8.8%). 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.
| 197 test files / 2,239 source files |
11% of recent commits change more than 2,000 lines
adequate155 of 1383 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.
| 155 commits over 2,000 lines |
Product & Engineering Maturity
adequate118 direct dependencies in a single manifest
adequatefrontend/package.json declares 118 direct dependencies. Each one is a maintenance obligation, a supply-chain surface and a potential licence question that transfers with the asset. The count says nothing about whether any given dependency was a good choice; it says how many such choices a buyer inherits.
frontend/package.json — 118 declared |
4% of bug fixes add or change a test
adequateOf 397 fixes in the last 24 months, 16 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.
| 16 of 397 |
Security & Reliability Posture
adequate1 credential-shaped string exists in the history
adequateMatches for JWT were committed at some point across 1,913 commits examined. Some of the files that held them are still in the working tree. What matters is whether each was rotated after it was committed. The code cannot tell whether any of them is live, and that decides whether this matters: none sits in production configuration, and none is in a format its provider keeps for live keys. Is any of these live? Show that each was rotated after it was committed, and when.
| JWT pattern added here |
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.
app-server/Dockerfile — runs as root |
1 environment file is committed
adequate.env is 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 |
The build runs third-party code it does not pin
adequate5 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/backend-build-and-test.yml:27 — action pinned by tag |
.github/workflows/backend-build-and-test.yml:38 — action pinned by tag |
2 SQL statements built from strings
adequate2 places in product code build SQL by formatting or joining strings rather than passing parameters. In each, what the code shows going in is a table or column name, a constant, or something the line does not show, not a request's value. Ask whether any value reaches these strings, rather than a parameter.
frontend/lib/telemetry/instance.ts:54 — SQL built from a string |
frontend/lib/telemetry/instance.ts:99 — SQL built from a string |
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 2,470 files for 10 structured logging libraries; 0 matched |
3 of 7 deployed images carry no version, or `latest`
adequate3 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.
docker-compose-local-dev-full.yml:8 — image without a version |
docker-compose.yml:128 — image without a version |
docker-compose.yml:70 — image without a version |
Fit with the Acquirer
not assessableNot rated: structurally not assessable from a repository.
Read more, or read your own
The full report on lmnr-ai/lmnr: 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.