Read 2026-11-03
graphite-project/graphite-web: technical due diligence, read from its repository
What Borehole read in graphite-project/graphite-web's code and history at b23b548: 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 | strong |
| Security & Reliability Posture | strong |
| Observability & Operations | not assessable |
| Fit with the Acquirer | not assessable |
What the repository says
- Releases are cut from another branch than the one surveyed
Architecture & Codebase — including AI provenance
strongwebapp/graphite/render/functions.py is 6,166 lines, 101× this codebase's median file
adequateThe median source file here is 61 lines. 6 files exceed 1,000 lines, the largest being 6,166. 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.
webapp/graphite/render/functions.py:1 — 6,166 lines (101× median) |
webapp/content/js/dashboard.js:1 — 3,678 lines (60× median) |
webapp/content/js/ext/adapter/ext/ext-base-debug.js:1 — 2,909 lines (47× median) |
webapp/graphite/render/glyph.py:1 — 2,022 lines (33× median) |
webapp/content/js/composer_widgets.js:1 — 1,552 lines (25× median) |
61 errors caught and discarded in product code
adequate61 places catch an error and do nothing with it, across 23 files (1.3 per thousand lines). Each is a failure the system will not report. They surface later as problems nobody can explain, and they are cheap to fix now.
setup.py:31 — error caught and discarded |
webapp/content/js/ace/ace.js:1 — error caught and discarded |
webapp/content/js/ace/ace.js:1 — error caught and discarded |
Engineering Process & SDLC Maturity
strongNo finding.
Product & Engineering Maturity
strongReleases are cut from another branch than the one surveyed
adequateThe newest release, 1.1.10, is not on the branch this survey read; the newest release on it is 1.1.0. The shipped product may differ from what this report describes. Survey the release branch too.
| tag 1.1.10 |
Security & Reliability Posture
strong22 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.
docs/requirements.txt:2 — any version |
docs/requirements.txt:3 — any version |
docs/requirements.txt:4 — any version |
docs/requirements.txt:5 — any version |
docs/requirements.txt:6 — any version |
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 graphite-project/graphite-web: 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.