Read 2026-11-03
jupyter/notebook: technical due diligence, read from its repository
What Borehole read in jupyter/notebook's code and history at b5a05a8: 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
strongpackages/application-extension/src/index.ts is 1,395 lines, 31× this codebase's median file
adequateThe median source file here is 45 lines. 2 files exceed 1,000 lines, the largest being 1,395. 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/application-extension/src/index.ts:1 — 1,395 lines (31× median) |
packages/notebook-extension/src/index.ts:1 — 1,010 lines (22× median) |
A move from JavaScript to TypeScript began 71 months ago and is 67% done
adequate33 product files are in the new language and 16 are still in the old one, 71 months after the first new file appeared. The new language's share of the lines rose from 3% to 92%, and moved 0 percentage points in the last year. Two languages for one job doubles what an engineer has to know, and the unmoved half is usually what nobody wants to touch. Ask whether finishing it is planned, and what it costs.
| 16 old, 33 new |
Engineering Process & SDLC Maturity
strongTests are retried until they pass
adequateThe suite is configured to retry failing tests (ui-tests/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.
ui-tests/playwright.config.ts:21 — test retry |
Product & Engineering Maturity
strongReleases are cut from another branch than the one surveyed
adequateThe newest release, v7.6.4, is not on the branch this survey read; the newest release on it is v7.6.0. The shipped product may differ from what this report describes. Survey the release branch too.
| tag v7.6.4 |
Security & Reliability Posture
strong16 locked dependencies have published vulnerabilities, 27 high or critical
adequate16 of 1,568 locked dependencies match 45 published advisories in OSV, 27 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. This lockfile pins development tools alongside what ships and does not say which is which, so some of these may never reach a user.
5 advisories against this project in the last 24 months, 4 high or critical
adequateThe newest was published on 2026-10-21. A project that publishes advisories is telling its users about its fixes, and the count and pace say how much security work it carries. Whether 5 of them are fixed in the code you ship could not be told from this history: its version is only known to be at least 7.6.0. Answer lives in: the release you run, set against each fixed version. The record is incomplete: NVD: 87 records name notebook with nothing tying them to this repository (CVE-2002-1969, CVE-2006-5882, CVE-2008-0706, …).
| 2026-10-21: CVE-2026-114140 (high): The nbconvert tool, jupyter nbconvert, converts Jupyter notebooks to various other formats via Jinja templates. From 5.4.0 until 7.17.2, ExtractOutputPreprocess |
| 2026-10-15: GHSA-jwrc-gm9j-263p (moderate), fixed in 7.6.3: JupyterLab: Command link trust prompt in JupyterLab can trust a document other than the one clicked |
| 2026-10-01: GHSA-6966-vjj6-99xv (high), fixed in 7.6.3: JupyterLab: Cross-site scripting (XSS) in JupyterLab via notebook cells pasted from the system clipboard |
| 2026-05-06: GHSA-mqcg-5x36-vfcg (high), fixed in 4.5.7: JupyterLab's command linker attributes in HTML enable one-click command execution from untrusted content |
| 2026-04-30: GHSA-rch3-82jr-f9w9 (high), fixed in 4.5.7: Jupyter Notebook Vulnerable to Authentication Token Theft via CommandLinker XSS |
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 jupyter/notebook: 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.