Read 2026-10-04
juliapluto/pluto.jl: technical due diligence, read from its repository
What Borehole read in juliapluto/pluto.jl's code and history at 3a7651f: 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
- Releases are cut from another branch than the one surveyed
README.md:204: names NumFOCUS
Architecture & Codebase — including AI provenance
strongfrontend/imports/CodemirrorPlutoSetup.d.ts is 8,651 lines, 75× this codebase's median file
adequateThe median source file here is 114 lines. 5 files exceed 1,140 lines, the largest being 8,651. 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.
frontend/imports/CodemirrorPlutoSetup.d.ts:1 — 8,651 lines (75× median) |
frontend/components/Editor.js:1 — 1,943 lines (17× median) |
frontend/components/CellInput/scopestate_statefield.js:1 — 1,387 lines (12× median) |
src/webserver/Firebasey.jl:1 — 1,270 lines (11× median) |
frontend/components/CellInput.js:1 — 1,167 lines (10× median) |
Engineering Process & SDLC Maturity
strongNo finding.
Product & Engineering Maturity
adequate10% of bug fixes add or change a test
adequateOf 100 fixes in the last 24 months, 10 touched a test. A fix without the test that would have caught the bug can quietly come back, and the suite never learns from what went wrong.
| 10 of 100 |
Releases are cut from another branch than the one surveyed
adequateThe newest release, v1.0.3, is not on the branch this survey read; the newest release on it is v0.20.1. The shipped product may differ from what this report describes. Survey the release branch too.
| tag v1.0.3 |
Security & Reliability Posture
adequate1 credential-shaped string committed to the tree
adequateMatches for Google API key appear in tracked files outside test and fixture paths. They stay in the history even after they leave the tree, so what matters is whether each was rotated. The code cannot tell whether any of them is live, and that decides whether this matters: none sits in production configuration, and none is in a format its provider keeps for live keys. Is any of these live? Show that each was rotated after it was committed, and when. Only Google API keys matched. Those are often public by design, in a browser app's Firebase or Maps configuration; the question is whether each is restricted to the app's domains and APIs.
| Google API key pattern matched |
The build runs third-party code it does not pin
adequate10 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/Bundle.yml:32 — action pinned by tag |
.github/workflows/FrontendTest.yml:29 — action pinned by tag |
2 locked dependencies have published vulnerabilities, 2 high or critical
adequate2 of 192 locked dependencies match 3 published advisories in OSV, 2 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: only the build reaches them: a bundler, a code generator, a build plugin, or a lockfile in a tooling directory.
frontend-bundler/package-lock.json — browserslist 4.28.1: GHSA-73wf-gq98-2v4g (high), fixed in 4.28.7; reached only by the build |
frontend-bundler/package-lock.json — baseline-browser-mapping 2.9.15: GHSA-w5vr-8v7q-w6rv (moderate), fixed in 2.11.0; reached only by the build |
Observability & Operations
not assessableNot rated: only 4 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 juliapluto/pluto.jl: 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.