Read 2026-10-28
mjmlio/mjml: technical due diligence, read from its repository
What Borehole read in mjmlio/mjml's code and history at 40ddfbb: 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 | 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
Architecture & Codebase — including AI provenance
strongpackages/mjml-core/src/index.js is 1,017 lines, 22× this codebase's median file
adequateThe median source file here is 46 lines. 1 file exceed 1,000 lines, the largest being 1,017. 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/mjml-core/src/index.js:1 — 1,017 lines (22× median) |
Engineering Process & SDLC Maturity
strongNo finding.
Product & Engineering Maturity
strongReleases are cut from another branch than the one surveyed
adequateThe newest pre-release, v6.0.0-alpha.1, is not on the branch this survey read; the newest release on it is v5.4.1. The shipped product may differ from what this report describes. Survey the release branch too.
| tag v6.0.0-alpha.1 |
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 246 tracked files; 0 present |
42 locked dependencies have published vulnerabilities, 52 high or critical
adequate42 of 1,391 locked dependencies match 95 published advisories in OSV, 52 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.
1 advisory against this project in the last 24 months
adequateThe newest was published on 2025-12-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. Whether 1 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 5.4.1. Answer lives in: the release you run, set against each fixed version. The record is incomplete: NVD: 2 records name mjml with nothing tying them to this repository (CVE-2024-25293, CVE-2024-26151).
| 2025-12-14: CVE-2025-67898 (moderate): MJML through 4.18.0 allows mj-include directory traversal to test file existence and (in the type="css" case) read files. NOTE: this issue exists because of an |
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 mjmlio/mjml: 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.