Borehole · Project · free tier
builderio/figma-html
Free reading: not for reliance
2b24434 · 235 commits · 33 files
Read 2026-11-03

builderio/figma-html: technical due diligence, read from its repository

What Borehole read in builderio/figma-html's code and history at 2b24434: 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.

DimensionRating
Architecture & Codebase — including AI provenancestrong
Engineering Process & SDLC Maturityadequate
Product & Engineering Maturitynot assessable
Security & Reliability Postureadequate
Observability & Operationsnot assessable
Fit with the Acquirernot assessable

Architecture & Codebase — including AI provenance

strong

No finding.

Engineering Process & SDLC Maturity

adequate
02.4

Nothing in the history is tagged as a release

adequate

Across 6.0 years of history there is not one tag. There may still be a deployment process, but this repository holds no record of what shipped when — which is the record a buyer needs to reconstruct an incident or a regression after the fact.

Evidence
0 tags across 235 commits and 2185 days
02.6

Almost no process scaffolding exists in the repository

adequate

Of five ordinary markers — CI workflows, CODEOWNERS, a pull-request template, pre-commit hooks, contribution guidance — 1 is present: CODEOWNERS. Branch protection itself is a GitHub setting rather than a file, so this is a reading of proxies and not of the rules themselves. What it does establish is that the process is not written down anywhere a new engineer would find it.

Evidence
1 of 5 markers present across 33 tracked files

Product & Engineering Maturity

not assessable
04.1

Change keeps returning to the same few files

adequate

Five files out of 117 absorb 37% of all file-level change. Concentration like this is where debt is usually being serviced rather than repaid: the same code is reopened because it is load-bearing, fragile, or both. A repository cannot tell you which — that is a conversation with the team.

Evidence
plugin/ui.tsx — 67 commits touched it
README.md — 45 commits touched it
package.json — 32 commits touched it
plugin/code.ts — 20 commits touched it
lib/html-to-figma/index.ts — 16 commits touched it
04.5

Effort is shifting from building to rewriting

adequate

Deleted lines per line added rose from 0.62 to 3.27 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.

Evidence
first half 0.62, second half 3.27 (split 2022-08-23)
04.17

Node.js 16 is past end of life

adequate

The code is pinned to Node.js 16 (end of life 2023-09-11). None of these receives security fixes any more; the first stopped on 2023-09-11. 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.

Evidence
.nvmrc — Node.js 16, end of life 2023-09-11

Security & Reliability Posture

adequate
05.26

11 locked dependencies have published vulnerabilities, 7 high or critical in what ships

adequate

11 of 177 locked dependencies match 16 published advisories in OSV, 7 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.

Evidence
chrome-extension/package-lock.json — braces 3.0.2: GHSA-grv7-fg5c-xmjg (high), fixed in 3.0.3
chrome-extension/package-lock.json — immutable 4.1.0: GHSA-v56q-mh7h-f735 (high), fixed in 4.3.9
chrome-extension/package-lock.json — lodash 4.17.21: GHSA-r5fr-rjxr-66jc (high), fixed in 4.18.0

Observability & Operations

not assessable

Not 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 assessable

Not rated: structurally not assessable from a repository.

Read more, or read your own

The full report on builderio/figma-html: 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.