Read 2026-10-04
phoenixframework/phoenix: technical due diligence, read from its repository
What Borehole read in phoenixframework/phoenix's code and history at 429796d: 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 | adequate |
| 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
stronglib/phoenix/controller.ex is 2,011 lines, 15× this codebase's median file
adequateThe median source file here is 130 lines. 5 files exceed 1,300 lines, the largest being 2,011. 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.
lib/phoenix/controller.ex:1 — 2,011 lines (15× median) |
priv/static/phoenix.js:1 — 1,725 lines (13× median) |
priv/static/phoenix.cjs.js:1 — 1,724 lines (13× median) |
priv/static/phoenix.mjs:1 — 1,702 lines (13× median) |
lib/phoenix/router.ex:1 — 1,521 lines (11× median) |
Engineering Process & SDLC Maturity
strongNo finding.
Product & Engineering Maturity
strongReleases are cut from another branch than the one surveyed
adequateThe newest release, v1.8.15, is not on the branch this survey read; the newest release on it is v1.8.8. The shipped product may differ from what this report describes. Survey the release branch too.
| tag v1.8.15 |
Security & Reliability Posture
strong3 locked dependencies have published vulnerabilities
adequate3 of 41 locked dependencies match 11 published advisories in OSV. 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, 2 high or critical
adequateThe newest was published on 2026-08-10. 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 2 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 1.8.8. Answer lives in: the release you run, set against each fixed version. EEF-CVE-2026-56812 (moderate), GHSA-6983-jfq8-485w (high) are fixed in the surveyed commit; which release carries them cannot be told from this history, which does not place the release users run. Answer lives in: the version you run. The record is incomplete: NVD: 42 records name phoenix with nothing tying them to this repository (CVE-2006-5090, CVE-2008-2533, CVE-2008-2534, …).
| 2026-08-10: CVE-2026-64941 (low): URL Redirection to Untrusted Site ('Open Redirect') vulnerability in phoenixframework phoenix_live_view allows an attacker to send a victim's browser to an orig |
| 2026-07-13: CVE-2026-58228 (moderate): Cross-site scripting vulnerability in phoenixframework phoenix_live_view allows an attacker to bypass URL scheme validation and execute JavaScript in a victim's |
| 2026-07-07: EEF-CVE-2026-56812 (moderate), fixed in 1.8.9: Phoenix JavaScript presence client crashes on presence keys colliding with Object.prototype members in Presence.syncState/syncDiff |
| 2026-07-07: GHSA-6983-jfq8-485w (high), fixed in 1.8.9: Unbounded channel joins per transport enables DoS over few connections |
| 2026-05-05: GHSA-628h-q48j-jr6q (high), fixed in 1.7.22: Long-poll NDJSON body splitting causes large memory allocation in Phoenix |
Observability & Operations
adequateOne request cannot be followed through the logs
adequateNothing in the service carries a request or correlation id, and there is no tracing. When a customer reports a failure, the log lines that belong to their request cannot be picked out from everyone else's.
| no request id, correlation id or tracing found |
No error reporter is wired in
adequateNothing in the service initialises an error reporter (Sentry, Rollbar, Bugsnag, Honeybadger or an APM agent). An exception in production reaches a person only if someone is reading the logs, which usually means a customer reports it first.
| no error reporter initialised |
Fit with the Acquirer
not assessableNot rated: structurally not assessable from a repository.
Read more, or read your own
The full report on phoenixframework/phoenix: 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.