Read 2026-10-22
logto-io/logto: technical due diligence, read from its repository
What Borehole read in logto-io/logto's code and history at c347c75: 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 | strong |
| Product & Engineering Maturity | adequate |
| Security & Reliability Posture | adequate |
| Observability & Operations | adequate |
| Fit with the Acquirer | not assessable |
Architecture & Codebase — including AI provenance
strongpackages/core/src/routes/experience/classes/experience-interaction.ts is 1,861 lines, 32× this codebase's median file
adequateThe median source file here is 57 lines. 1 file exceed 1,000 lines, the largest being 1,861. 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.
packages/core/src/routes/experience/classes/experience-interaction.ts:1 — 1,861 lines (32× median) |
Engineering Process & SDLC Maturity
strongTests are retried until they pass
adequateThe suite is configured to retry failing tests (packages/core/src/libraries/hook/index.test.ts). A retry turns a flaky test green without saying why it failed, so a green build means the tests passed eventually. Ask how many retries a typical run needs, and which tests need them.
packages/core/src/libraries/hook/index.test.ts:41 — test retry |
Product & Engineering Maturity
adequate2 jobs are each done by more than one library
adequateWithin a single package: HTTP clients: got, ky; dates: date-fns, dayjs. Each duplicate is bundle size, two ways of doing the same thing in one codebase, and two upgrade paths to maintain. It is usually the residue of a migration that stopped halfway.
packages/account/package.json — several libraries per job |
packages/cli/package.json — several libraries per job |
26 files still carry code deprecated more than two years ago
adequate26 files were marked deprecated over two years ago and still are, the oldest since Jan 2023. A deprecation is a promise to remove. Ask what still depends on these, and whether removing them is scheduled.
packages/core/src/queries/oidc-model-instance.ts — deprecated since Jan 2023 |
packages/schemas/src/seeds/management-api.ts — deprecated since Feb 2023 |
packages/schemas/src/seeds/sign-in-experience.ts — deprecated since Feb 2023 |
packages/phrases/src/locales/en/errors/oidc.ts — deprecated since Sep 2023 |
packages/schemas/src/foundations/jsonb-types/hooks.ts — deprecated since Oct 2023 |
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
adequate18 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/alteration-compatibility-integration-test.yml:55 — action pinned by tag |
.github/workflows/alteration-compatibility-integration-test.yml:90 — action pinned by tag |
3 shell commands built from strings
adequate3 places run a command through a shell (`shell=True`, `os.system`, `exec` with a template) rather than passing arguments. Where any part comes from outside, it is command injection. Ask where each one's input comes from.
.scripts/publish.js:28 — command run through a shell |
.scripts/publish.js:35 — command run through a shell |
.scripts/publish.js:40 — command run through a shell |
8 locked dependencies have published vulnerabilities, 5 high or critical in what ships
adequate8 of 2,462 locked dependencies match 16 published advisories in OSV, 8 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.
pnpm-lock.yaml — braces 3.0.3: GHSA-vfj7-8cjw-p6xm (high) |
pnpm-lock.yaml — follow-redirects 1.16.0: GHSA-8r9p-f939-6h3c (high), fixed in 1.16.1 |
pnpm-lock.yaml — http-cache-semantics 4.1.1: GHSA-ch52-4w7c-c8xp (high) |
21 advisories against this project in the last 24 months, 18 high or critical
adequateThe newest was published on 2026-09-01. 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 6 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 1.45.0. Answer lives in: the release you run, set against each fixed version.
| 2026-09-01: GHSA-vrv3-3j98-vfpp (high), fixed in 1.43.0: Token exchange accepts an ID token as an access-token subject and ignores the subject token's issuing client, widening a consented credential into the user's fu |
| 2026-09-01: GHSA-crc8-q4hm-4564 (high), fixed in 1.43.0: Third-party application with only the openid scope can set an initial password on a passwordless, email-less, phone-less account, enabling account takeover |
| 2026-09-01: GHSA-p88q-p28c-j9jf (high), fixed in 1.43.0: OAuth/SSO authorization-code exfiltration and cross-session account takeover via attacker-controlled native_callback parameter in social/SSO landing flow |
| 2026-09-01: GHSA-5wr4-942j-h43m (high), fixed in 1.43.0: JWT Customizer node:vm execution has no effective timeout, allowing full-process or tenant-wide DoS |
| 2026-09-01: GHSA-6g9q-qrx7-3jxf (high), fixed in 1.42.0: Account API can disclose stored third-party provider tokens without the identities scope |
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 6,816 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 |
The code branches on the environment's name at 66 places
adequate66 places outside configuration test whether they are running in production or staging. Staging then does not exercise production's code, and each deploy is the first run of those branches. Differences belong in configuration the code reads, not in the code.
packages/account/src/constants/env.ts:6 — branch on the environment name |
packages/account/src/constants/env.ts:9 — branch on the environment name |
packages/console/src/consts/env.ts:8 — branch on the environment name |
Fit with the Acquirer
not assessableNot rated: structurally not assessable from a repository.
Read more, or read your own
The full report on logto-io/logto: 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.