Read 2026-11-03
gridaco/grida: technical due diligence, read from its repository
What Borehole read in gridaco/grida's code and history at 9cbacac: 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 | not assessable |
| Fit with the Acquirer | not assessable |
Architecture & Codebase — including AI provenance
strongservices/grida-canvas-document-worker-cf/worker-configuration.d.ts is 12,856 lines, 133× this codebase's median file
adequateThe median source file here is 96 lines. 76 files exceed 1,000 lines, the largest being 12,856. 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.
services/grida-canvas-document-worker-cf/worker-configuration.d.ts:1 — 12,856 lines (133× median) |
.ref/figma/figma-plugin-api.d.ts:1 — 11,223 lines (116× median) |
packages/grida-canvas-io-figma/fig-kiwi/schema.ts:1 — 10,285 lines (107× median) |
packages/grida-cmath/index.ts:1 — 7,924 lines (82× median) |
.ref/figma/figma-rest-api.d.ts:1 — 7,352 lines (76× median) |
Engineering Process & SDLC Maturity
adequate26% of commit subjects say nothing about the change
adequate2,623 of 10,258 subjects are either under twelve characters or one of the standard placeholders — wip, fix, update. The history is therefore not usable for reconstructing why a decision was taken, which is the main thing an inheriting engineer needs it for. It says nothing about code quality and a great deal about how much context transfers with the asset.
| 2,623/10,258 low-content subjects (25.6%) |
| 'logo added' |
| 'added docs' |
| 'added CNAME' |
| 'cleanup' |
Tests are retried until they pass
adequateThe suite is configured to retry failing tests (editor/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.
editor/playwright.config.ts:19 — test retry |
Product & Engineering Maturity
adequate226 direct dependencies in a single manifest
adequateeditor/package.json declares 226 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.
editor/package.json — 226 declared |
packages/ui/package.json — 28 declared |
packages/grida-ai-agent/package.json — 15 declared |
apps/api/package.json — 13 declared |
Security & Reliability Posture
adequateThe 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/api.yml:26 — action pinned by tag |
.github/workflows/database-tests.yml:20 — action pinned by tag |
78 locked dependencies have published vulnerabilities, 55 high or critical in what ships
adequate78 of 3,857 locked dependencies match 180 published advisories in OSV, 85 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 — next 16.2.6: GHSA-2464-fhr4-w9xw (critical), fixed in 16.4.1 |
pnpm-lock.yaml — tinypool 1.1.1: GHSA-5gmw-xhrv-c9v3 (critical), fixed in 2.1.1 |
pnpm-lock.yaml — @vitest/browser 4.0.18: GHSA-2h32-95rg-cppp (critical), fixed in 4.1.6; a development dependency |
63 places insert HTML from a variable without sanitising it
adequate63 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.
editor/app/(dev)/ui/components/hud/_showcase.tsx:2723 — HTML from a variable |
editor/app/(tenant)/~/[tenant]/(e)/d/e/[id]/layout.tsx:127 — HTML from a variable |
editor/app/(tenant)/~/[tenant]/(e)/d/e/[id]/layout.tsx:136 — HTML from a variable |
Observability & Operations
not assessableNot rated: only 5 of 16 checks could reach a conclusion here; the rest do not apply to this repository or could not read it.
Fit with the Acquirer
not assessableNot rated: structurally not assessable from a repository.
Read more, or read your own
The full report on gridaco/grida: 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.