mjml-core
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:html-minifier | AI (dependencies): html-minifier is a well-known, widely-used HTML minification library; its use in mjml-core for email HTML output is expected and appropriate. | ai | |
| semgrep | semgrep:dynamic-require | AI (semgrep): Dynamic require in mjmlconfig.js loads a user-specified config file by design — standard config-loader pattern, not an injection risk. Stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:cssnano | AI (phantom-deps): cssnano is explicitly declared as a runtime dependency in package.json; used indirectly via cssnano-preset-lite. Not a true phantom dependency. | ai | |
| phantom-deps | phantom-dep:postcss | AI (phantom-deps): postcss is explicitly declared as a runtime dependency in package.json; used indirectly via htmlnano/cssnano pipeline. Not a true phantom dependency. | ai |
Versions (showing 11 of 11)
| Version | Deps | Published |
|---|---|---|
| 5.3.0 | 12 / 3 | |
| 5.2.2 | 12 / 3 | |
| 5.2.1 | 12 / 3 | |
| 5.2.0 | 12 / 3 | |
| 5.1.0 | 13 / 3 | |
| 5.0.1 | 12 / 3 | |
| 5.0.0 | 12 / 3 | |
| 4.18.0 | 10 / 3 | |
| 4.17.2 | 10 / 3 | |
| 4.17.1 | 10 / 3 | |
| 4.17.0 | 10 / 3 |
v5.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.2.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.18.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.17.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.17.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.17.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.