Read 2026-10-23
uselotus/lotus: technical due diligence, read from its repository
What Borehole read in uselotus/lotus's code and history at 9c4fe5d: 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
strongfrontend/src/gen-types-camel.ts is 9,539 lines, 179× this codebase's median file
adequateThe median source file here is 53 lines. 16 files exceed 1,000 lines, the largest being 9,539. 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.
frontend/src/gen-types-camel.ts:1 — 9,539 lines (179× median) |
frontend/src/gen-types.ts:1 — 9,539 lines (179× median) |
backend/metering_billing/models.py:1 — 4,145 lines (78× median) |
backend/api/serializers/model_serializers.py:1 — 2,827 lines (53× median) |
backend/metering_billing/demos.py:1 — 2,723 lines (51× median) |
Engineering Process & SDLC Maturity
adequateTests cover a thin slice of the codebase
adequate21 test files against 552 source files (3.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.
| 21 test files / 552 source files |
Product & Engineering Maturity
strongEffort is shifting from building to rewriting
adequateDeleted lines per line added rose from 0.28 to 1.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.28, second half 1.00 (split 2024-07-31) |
3 pinned runtimes are past end of life
adequateThe code is pinned to Go 1.20 (end of life 2024-02-06); Node.js 18 (end of life 2025-04-30); Python 3.9 (end of life 2025-10-31). None of these receives security fixes any more; the first stopped on 2024-02-06. Moving off an unsupported runtime is rarely a one-line change, so a buyer should ask whether the upgrade is planned and what it touches.
go/event-guidance/Dockerfile — Go 1.20, end of life 2024-02-06 |
frontend/Dockerfile — Node.js 18, end of life 2025-04-30 |
backend/Dockerfile — Python 3.9, end of life 2025-10-31 |
Security & Reliability Posture
adequate3 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.
backend/Dockerfile — runs as root |
frontend/Dockerfile — runs as root |
proxy/Dockerfile — runs as root |
The build runs third-party code it does not pin
adequate3 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/cypress.yml:57 — action pinned by tag |
.github/workflows/cypress.yml:98 — action pinned by tag |
8 outbound calls can wait forever
adequate8 HTTP calls use a client with no timeout (Python `requests` without `timeout=`, or Go's default client). When a dependency slows down, each one holds a worker until the connection gives up, and enough of them take the service down with the dependency.
backend/metering_billing/payment_processors.py:302 — outbound call without a timeout |
backend/metering_billing/payment_processors.py:313 — outbound call without a timeout |
backend/metering_billing/views/crm_views.py:133 — outbound call without a timeout |
55 locked dependencies have published vulnerabilities, 32 high or critical in what ships
adequate55 of 1,272 locked dependencies match 137 published advisories in OSV, 67 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. This lockfile pins development tools alongside what ships and does not say which is which, so some of these may never reach a user.
backend/poetry.lock — certifi 2023.5.7: GHSA-6q48-6c7w-9gw2 (critical), fixed in 2026.10.19 |
backend/poetry.lock — pillow 9.5.0: GHSA-332p-7hrc-92wf (critical), fixed in 13.0.0 |
go/event-guidance/go.mod — golang.org/x/crypto v0.7.0: GHSA-5cgq-3rg8-m6cv (critical), fixed in 0.52.0 |
6 advisories against this project in the last 24 months, 5 high or critical
adequateThe newest was published on 2026-10-22. A project that publishes advisories is telling its users about its fixes, and the count and pace say how much security work it carries. Whether 5 of them are fixed in the code you ship could not be told from this history: its version is only known to be at least 0.10.2. Answer lives in: the release you run, set against each fixed version. The record is incomplete: NVD: 264 records name lotus with nothing tying them to this repository (CVE-1999-0429, CVE-1999-0729, CVE-1999-1275, …).
| 2026-10-22: CVE-2026-115329 (moderate): Lotus through 0.10.2 contains an insecure direct object reference vulnerability in SubscriptionViewSet.get_object() that uses an unscoped queryset without organ |
| 2026-10-22: CVE-2026-115330 (high): Lotus through 0.10.2 contains an sql injection vulnerability that allows authenticated organization users to execute arbitrary SQL by appending stacked statemen |
| 2026-10-22: CVE-2026-115331 (high): Lotus through 0.10.2 contains an sql injection vulnerability that allows authenticated organization users to inject SQL by supplying crafted billable metric pro |
| 2026-10-22: CVE-2026-115332 (high): Lotus through 0.10.2 contains an sql injection vulnerability that allows authenticated organization users to inject SQL by registering crafted subscription_filt |
| 2026-10-22: CVE-2026-115333 (high): Lotus through 0.10.2 contains an improper authentication vulnerability in the Go event ingestion middleware that validates API keys by prefix only, without chec |
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 615 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 |
Fit with the Acquirer
not assessableNot rated: structurally not assessable from a repository.
Read more, or read your own
The full report on uselotus/lotus: 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.