Read 2026-11-03
gitbookio/gitbook: technical due diligence, read from its repository
What Borehole read in gitbookio/gitbook's code and history at 123454d: 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 | not assessable |
| Fit with the Acquirer | not assessable |
What the repository says
- No release for 12 months while development continues
Architecture & Codebase — including AI provenance
strongpackages/react-openapi/src/OpenAPISchema.tsx is 1,315 lines, 21× this codebase's median file
adequateThe median source file here is 62 lines. 3 files exceed 1,000 lines, the largest being 1,315. 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/react-openapi/src/OpenAPISchema.tsx:1 — 1,315 lines (21× median) |
packages/gitbook/src/middleware.ts:1 — 1,093 lines (17× median) |
packages/gitbook/src/lib/references.tsx:1 — 1,029 lines (16× median) |
Engineering Process & SDLC Maturity
strongTests are retried until they pass
adequateThe suite is configured to retry failing tests (packages/gitbook/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/gitbook/playwright.config.ts:7 — test retry |
Product & Engineering Maturity
adequate81 direct dependencies in a single manifest
adequatepackages/gitbook/package.json declares 81 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/gitbook/package.json — 81 declared |
packages/react-openapi/package.json — 12 declared |
packages/expr/package.json — 6 declared |
packages/react-contentkit/package.json — 4 declared |
No release for 12 months while development continues
adequateThe last tag, @gitbook/react-openapi@1.5.2, was cut 384 days before the survey; the typical gap between releases was 0 days, and 222 commits landed in the last 90 days. Users run the last release, not this code.
| last tag @gitbook/react-openapi@1.5.2 |
Security & Reliability Posture
adequateNone of the standard security guard rails are configured
adequateThere is no disclosure policy, no automated dependency updates, no named code owners and no pre-commit configuration. None of these is load-bearing on its own. Their collective absence says that security posture here is whatever the current team happens to remember to do, which is not a posture that survives the team changing.
| checked 5 kinds of guard rail across 1,233 tracked files; 0 present |
135 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.
package.json:5 — ^22.3.0 |
package.json:8 — ^2.31.1 |
package.json:9 — ^0.62.0 |
package.json:10 — ^1.90.0 |
package.json:11 — ^2.11.10 |
The build runs third-party code it does not pin
adequate4 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/deploy-preview.yaml:91 — action pinned by tag |
.github/workflows/deploy-preview.yaml:99 — action pinned by tag |
12 places insert HTML from a variable without sanitising it
adequate12 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/gitbook/src/components/Announcement/AnnouncementDismissedScript.tsx:35 — HTML from a variable |
packages/gitbook/src/components/DocumentView/CodeBlock/MermaidCodeBlock.tsx:96 — HTML from a variable |
packages/gitbook/src/components/DocumentView/Embed.tsx:39 — 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 gitbookio/gitbook: 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.