Read 2026-10-23
plotly/plotly.py: technical due diligence, read from its repository
What Borehole read in plotly/plotly.py's code and history at fcc3c8e: 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 | strong |
| Security & Reliability Posture | strong |
| Observability & Operations | not assessable |
| Fit with the Acquirer | not assessable |
Architecture & Codebase — including AI provenance
strongplotly/graph_objs/_figurewidget.py is 21,918 lines, 159× this codebase's median file
adequateThe median source file here is 137 lines. 99 files exceed 1,370 lines, the largest being 21,918. 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.
plotly/graph_objs/_figurewidget.py:1 — 21,918 lines (159× median) |
plotly/graph_objs/_figure.py:1 — 21,914 lines (159× median) |
plotly/basedatatypes.py:1 — 6,348 lines (46× median) |
plotly/graph_objs/layout/_yaxis.py:1 — 3,544 lines (25× median) |
plotly/graph_objs/_layout.py:1 — 3,529 lines (25× median) |
Engineering Process & SDLC Maturity
adequateTests cover a thin slice of the codebase
adequate157 test files against 1,679 source files (9.4%). This does not measure whether the tests are good, only whether enough of them exist for the codebase to be changed safely by someone who did not write it — which is exactly the situation after an acquisition.
| 157 test files / 1,679 source files |
Product & Engineering Maturity
strongEffort is shifting from building to rewriting
adequateDeleted lines per line added rose from 0.61 to 1.12 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.
| first half 0.61, second half 1.12 (split 2020-05-07) |
Security & Reliability Posture
strong39 locked dependencies have published vulnerabilities, 143 high or critical
adequate39 of 610 locked dependencies match 226 published advisories in OSV, 143 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. None of the high or critical ones is in what the product ships: they are optional extras of a package, installed only on request.
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 plotly/plotly.py: 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.