Read 2026-10-04
twentyhq/twenty: technical due diligence, read from its repository
What Borehole read in twentyhq/twenty's code and history at 6959dc8: 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 |
What the repository says
- Releases are cut from another branch than the one surveyed
LICENSE: Relicensed: MIT → AGPL-3.0 (2023-07-17)
Architecture & Codebase — including AI provenance
strongpackages/twenty-server/src/engine/workspace-manager/dev-seeder/data/constants/person-data-seeds.constant.ts is 20,496 lines, 602× this codebase's median file
adequateThe median source file here is 34 lines. 46 files exceed 1,000 lines, the largest being 20,496. 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/twenty-server/src/engine/workspace-manager/dev-seeder/data/constants/person-data-seeds.constant.ts:1 — 20,496 lines (602× median) |
packages/twenty-server/src/utils/email-providers.ts:1 — 16,349 lines (480× median) |
packages/twenty-ui/src/icon/providers/internal/AllIcons.ts:1 — 8,382 lines (246× median) |
packages/twenty-server/src/engine/workspace-manager/dev-seeder/data/constants/company-data-seeds.constant.ts:1 — 7,937 lines (233× median) |
packages/twenty-front/src/modules/onboarding/components/WelcomeOverlay/welcomeHalftoneDots.ts:1 — 2,905 lines (85× median) |
Engineering Process & SDLC Maturity
adequateTests are retried until they pass
adequateThe suite is configured to retry failing tests (packages/twenty-apps/examples/media-notes/playwright.config.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/twenty-apps/examples/media-notes/playwright.config.ts:12 — test retry |
7% of recent commits change more than 2,000 lines
adequate657 of 9130 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.
| 657 commits over 2,000 lines |
Product & Engineering Maturity
adequate155 direct dependencies in a single manifest
adequatepackages/twenty-server/package.json declares 155 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.
packages/twenty-server/package.json — 155 declared |
packages/twenty-front/package.json — 120 declared |
packages/twenty-server/src/engine/core-modules/application/application-package/constants/seed-dependencies/package.json — 41 declared |
packages/twenty-website/package.json — 23 declared |
3 jobs are each done by more than one library
adequateWithin a single package: CSS-in-JS: emotion, styled-components; HTTP clients: axios, node-fetch; UI component kits: chakra, mui. 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/twenty-apps/public/call-recorder/package.json — several libraries per job |
packages/twenty-apps/public/fireflies/package.json — several libraries per job |
Releases are cut from another branch than the one surveyed
adequateThe newest release, twenty/v2.42.6, is not on the branch this survey read; the newest release on it is twenty/v2.42.0. The shipped product may differ from what this report describes. Survey the release branch too.
| tag twenty/v2.42.6 |
Security & Reliability Posture
adequate7 credential-shaped strings committed to the tree
adequateMatches for JWT appear in tracked files outside test and fixture paths. They stay in the history even after they leave the tree, so what matters is whether each was rotated. 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. Every match is in CI configuration, where the usual reason is a throwaway service container's credential. Worth confirming; not a leak on its own. 1 other match set aside: expired tokens, licence tokens a vendor verifies with a public key, or placeholder text where a key would go. None grants access to anything.
| 5 cited: JWT pattern matched |
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.
packages/twenty-docker/twenty-postgres-spilo/Dockerfile — runs as root |
78 SQL statements built from strings
adequate78 places in product code build SQL by formatting or joining strings rather than passing parameters, and in 8 of them a value, not a table or column name, goes into the string. Where any of those values comes from a request, it is an injection point. Each site needs a look; the fix, parameters, is small.
5 shell commands built from strings
adequate5 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.
packages/twenty-sdk/src/cli/commands/docker/index.ts:52 — command run through a shell |
packages/twenty-sdk/src/cli/commands/docker/index.ts:128 — command run through a shell |
packages/twenty-sdk/src/cli/commands/docker/index.ts:132 — command run through a shell |
34 locked dependencies have published vulnerabilities, 59 high or critical
adequate34 of 5,295 locked dependencies match 133 published advisories in OSV, 59 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.
6 places insert HTML from a variable without sanitising it
adequate6 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.
packages/twenty-emails/src/utils/email-renderer/email-renderer.tsx:49 — HTML from a variable |
packages/twenty-emails/src/utils/email-renderer/nodes/html.tsx:11 — HTML from a variable |
packages/twenty-front/src/modules/support/hooks/useInstantiateSupportChat.ts:31 — HTML from a variable |
Relicensed: MIT → AGPL-3.0 (2023-07-17)
adequateThe root licence changed 1 time(s). The latest terms restrict what users, hosts or a buyer may do in ways the earlier ones did not. Code taken under the old terms stays under them, so both matter in diligence.
11 advisories against this project in the last 24 months, 6 high or critical
adequateThe newest was published on 2026-09-16. 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 7 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 2.42.0. Answer lives in: the release you run, set against each fixed version. The record is incomplete: NVD: 6 records name twenty with nothing tying them to this repository (CVE-2015-9536, CVE-2023-5162, CVE-2026-102716, …).
| 2026-09-16: CVE-2026-92771 (high): Twenty before 2.35.0 fails to validate field and row permissions in the groupBy-with-records GraphQL resolver, allowing authenticated users to bypass permission |
| 2026-09-02: GHSA-v93q-4jcx-7p9m (moderate), fixed in 2.22.0: Field-level read bypass via filter predicate (boolean/count oracle) |
| 2026-09-01: GHSA-mq5c-qp77-2cv3 (critical), fixed in 2.7.0: Plaintext IMAP/SMTP/CalDAV password disclosure to any workspace member via /metadata GraphQL |
| 2026-08-28: CVE-2026-82274 (moderate): Twenty through 2.35.0 contains an open redirect vulnerability in the OAuthPropagatorController.propagateOAuthCallback endpoint that treats the state query param |
| 2026-07-27: GHSA-mm7j-q9q3-qqwj (critical), fixed in 2.15.0: SQL Injection in Twenty `searchVector` Field Settings Allows Arbitrary PostgreSQL Execution |
Observability & Operations
adequate4 of 5 deployed images carry no version, or `latest`
adequate4 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.
packages/twenty-docker/helm/twenty/values.yaml:146 — image without a version |
packages/twenty-docker/k8s/manifests/deployment-db.yaml:30 — image without a version |
packages/twenty-docker/k8s/manifests/deployment-redis.yaml:26 — image without a version |
Readiness and liveness probes are identical in 1 of 1 workloads
adequateBoth probes call the same endpoint. When a dependency slows down, the liveness probe fails with the readiness probe, so the platform restarts pods that only needed taking out of rotation, and a partial outage becomes a full one. Liveness should ask whether the process is alive; readiness whether it can serve.
packages/twenty-docker/helm/twenty/values.yaml — same probe endpoint twice |
6 of 8 deployments run a single replica
adequate6 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.
Fit with the Acquirer
not assessableNot rated: structurally not assessable from a repository.
Read more, or read your own
The full report on twentyhq/twenty: 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.