Read 2026-10-04
mojolicious/mojo: technical due diligence, read from its repository
What Borehole read in mojolicious/mojo's code and history at 93f5917: 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 | not assessable |
| Security & Reliability Posture | adequate |
| Observability & Operations | not assessable |
| Fit with the Acquirer | not assessable |
Architecture & Codebase — including AI provenance
strongNo finding.
Engineering Process & SDLC Maturity
strongNo finding.
Product & Engineering Maturity
not assessableNot rated: only 8 of 19 checks could reach a conclusion here; the rest do not apply to this repository or could not read it.
Security & Reliability Posture
adequateNone of the standard security guard rails are configured
adequateThere 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.
| checked 5 kinds of guard rail across 407 tracked files; 0 present |
1 Dockerfile runs the application as root
adequateNo USER instruction switches away from root, so the process runs with full privileges inside the container. It is a one-line fix and an ordinary expectation, which is why its absence is worth asking about: it usually says more about whether anyone has reviewed the deployment than about this container specifically.
lib/Mojolicious/Command/Author/generate/dockerfile.pm — runs as root |
6 advisories against this project in the last 24 months, 3 high or critical
adequateThe newest was published on 2026-07-14. A project that publishes advisories is telling its users about its fixes, and the count and pace say how much security work it carries. None of them affects the surveyed version. The record is incomplete: NVD: 3 records name mojo with nothing tying them to this repository (CVE-2002-2193, CVE-2025-23850, CVE-2026-9537).
| 2026-07-14: GHSA-cf46-h6jw-mj3r (moderate), fixed in 9.48: CSRF tokens in Mojolicious are vulnerable to BREACH attacks |
| 2026-07-14: CVE-2026-15747 (critical): Mojolicious versions from 4.59 before 9.48 for Perl expose a stable representation of the session CSRF token to a BREACH compression oracle. _csrf_token genera |
| 2026-07-06: CVE-2026-14803 (moderate): Mojo::JSON versions before 9.47 for Perl allow memory exhaustion via unbounded recursion in the pure-Perl decoder. The pure-Perl decode path (`_decode_value` d |
| 2026-07-05: GHSA-p5qf-qvw8-xgvg (high), fixed in 9.47: Mojolicious pure-Perl Mojo::JSON decoder allows memory exhaustion via deeply nested data |
| 2025-05-03: CVE-2024-58135 (moderate): Mojolicious versions from 7.28 through 9.45 for Perl will generate weak HMAC session cookie secrets via "mojo generate app" by default. When creating a default |
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 mojolicious/mojo: 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.