Borehole · Project · free tier
phoenixframework/phoenix_live_dashboard
Free reading: not for reliance
83a0bd1 · 774 commits · 134 files
Read 2026-11-07

phoenixframework/phoenix_live_dashboard: technical due diligence, read from its repository

What Borehole read in phoenixframework/phoenix_live_dashboard's code and history at 83a0bd1: 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.

DimensionRating
Architecture & Codebase — including AI provenancestrong
Engineering Process & SDLC Maturityadequate
Product & Engineering Maturitynot assessable
Security & Reliability Postureadequate
Observability & Operationsnot assessable
Fit with the Acquirernot assessable

Architecture & Codebase — including AI provenance

strong
01.6

lib/phoenix/live_dashboard/page_builder.ex is 1,168 lines, 12× this codebase's median file

adequate

The median source file here is 92 lines. 1 file exceed 1,000 lines, the largest being 1,168. 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.

Evidence
lib/phoenix/live_dashboard/page_builder.ex:1 — 1,168 lines (12× median)

Engineering Process & SDLC Maturity

adequate
02.6

Almost no process scaffolding exists in the repository

adequate

Of five ordinary markers — CI workflows, CODEOWNERS, a pull-request template, pre-commit hooks, contribution guidance — 1 is present: CI workflows. Branch protection itself is a GitHub setting rather than a file, so this is a reading of proxies and not of the rules themselves. What it does establish is that the process is not written down anywhere a new engineer would find it.

Evidence
1 of 5 markers present across 134 tracked files
02.29

Pinned dependencies have not moved in 27 months

adequate

The lockfile last changed 817 days before the newest commit, and 56 commits have landed since. Every security fix published upstream in that time is absent until someone updates it, and the longer the gap the larger and riskier that update becomes.

Evidence
assets/package-lock.json last changed 2024-06-21

Product & Engineering Maturity

not assessable

Not rated: only 9 of 19 checks could reach a conclusion here; the rest do not apply to this repository or could not read it.

Security & Reliability Posture

adequate
05.2

None of the standard security guard rails are configured

adequate

There 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.

Evidence
checked 5 kinds of guard rail across 134 tracked files; 0 present
05.26

8 locked dependencies have published vulnerabilities, 1 high or critical in what ships

adequate

8 of 55 locked dependencies match 11 published advisories in OSV, 1 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.

Evidence
assets/package-lock.json — uplot 1.6.22: GHSA-34q8-jcq6-mc37 (high), fixed in 1.6.31
mix.lock — cowlib 2.19.0: EEF-CVE-2026-43966 (moderate)
mix.lock — cowboy 2.18.0: EEF-CVE-2026-115701 (unrated)

Observability & Operations

not assessable

Not 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 assessable

Not rated: structurally not assessable from a repository.

Read more, or read your own

The full report on phoenixframework/phoenix_live_dashboard: 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.