Read 2026-11-03
onlook-dev/onlook: technical due diligence, read from its repository
What Borehole read in onlook-dev/onlook's code and history at 423e2e9: 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 |
What the repository says
- Releases are cut from another branch than the one surveyed
.gitmodules:1: 1 submodule(s) this survey does not read: apps/admin
Architecture & Codebase — including AI provenance
strongpackages/fonts/src/family.ts is 19,752 lines, 438× this codebase's median file
adequateThe median source file here is 45 lines. 7 files exceed 1,000 lines, the largest being 19,752. 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/fonts/src/family.ts:1 — 19,752 lines (438× median) |
packages/ui/src/components/icons/index.tsx:1 — 3,668 lines (81× median) |
packages/utility/src/tailwind.ts:1 — 3,535 lines (78× median) |
apps/web/client/src/components/store/editor/theme/index.ts:1 — 1,216 lines (27× median) |
packages/models/src/supabase/db.ts:1 — 1,131 lines (25× median) |
Engineering Process & SDLC Maturity
strongNo finding.
Product & Engineering Maturity
adequate83 direct dependencies in a single manifest
adequateapps/web/client/package.json declares 83 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.
apps/web/client/package.json — 83 declared |
packages/ui/package.json — 63 declared |
packages/utility/package.json — 12 declared |
tooling/eslint/package.json — 12 declared |
9% of bug fixes add or change a test
adequateOf 345 fixes in the last 24 months, 30 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.
| 30 of 345 |
Releases are cut from another branch than the one surveyed
adequateThe newest release, v0.2.33, is not on the branch this survey read; the newest release on it is v0.2.32. The shipped product may differ from what this report describes. Survey the release branch too.
| tag v0.2.33 |
Security & Reliability Posture
adequate368 dependencies float, and no lockfile is committed
adequateDependency versions are declared as ranges and no lockfile is committed, so a build today does not necessarily produce what a build last month produced. That matters twice over in a transaction: the thing being bought cannot be reproduced exactly, and a compromised upstream release arrives without anyone choosing to take it.
apps/backend/package.json:15 — * |
apps/backend/package.json:17 — ^2.45.5 |
apps/backend/package.json:20 — ^5.0.0 |
apps/web/client/package.json:35 — ^3.0.10 |
apps/web/client/package.json:37 — ^6.2.0 |
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.
Dockerfile — runs as root |
apps/web/preload/Dockerfile — runs as root |
apps/web/server/Dockerfile — runs as root |
1 workload setting can give a container the host, behind a chart value or in a stack built from source
adequate1 places run a container privileged or in the host's namespaces only when a Helm value switches them on, or in a compose file that builds the product from this repository, which is how it is developed rather than how it ships. Neither is on by default in what ships. Ask whether production sets the value or runs that stack.
docker-compose.yml:13 — host access behind a setting or in a local stack |
25 places insert HTML from a variable without sanitising it
adequate25 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.
apps/web/client/public/onlook-preload-script.js:23 — HTML from a variable |
apps/web/client/src/app/_components/landing-page/code-one-to-one-section.tsx:99 — HTML from a variable |
apps/web/client/src/app/about/layout.tsx:163 — HTML from a variable |
4 advisories against this project in the last 24 months, 2 high or critical
adequateThe newest was published on 2026-07-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. None of them affects the surveyed version. The record is incomplete: NVD: 3 records name onlook with nothing tying them to this repository (CVE-2025-63783, CVE-2025-63784, CVE-2025-63785).
| 2026-07-22: CVE-2026-65013 (high): Onlook through 0.2.32, fixed in commit 423e2e9, contains a broken object level authorization vulnerability that allows authenticated attackers to access and man |
| 2025-12-14: GHSA-q42p-j3fm-rvq8 (moderate), fixed in >= 2025-12-14: Open Redirect in OAuth Callback Handler |
| 2025-12-14: GHSA-w73g-vc27-2pg2 (moderate), fixed in >= 2025-12-14: DOM-based Cross-Site Scripting (XSS) in Text Editor |
| 2025-12-14: GHSA-82m4-w39c-pgq6 (high), fixed in >= 2025-12-14: Broken Object Level Authorization in Project Mutation APIs |
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 1,565 files for 10 structured logging libraries; 0 matched |
Fit with the Acquirer
not assessableNot rated: structurally not assessable from a repository.
Read more, or read your own
The full report on onlook-dev/onlook: 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.