mjml
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:mjml-cli | AI (phantom-deps): mjml-cli is a first-party sibling package in the mjml monorepo; it is exposed via the bin entry rather than imported directly in JS, making the phantom-dep finding a stable false positive for this package. | ai | |
| provenance | no-provenance | AI (provenance): mjml is a long-established package (3739 days, 182 versions) that has never used Sigstore provenance; absence is expected and not a risk signal for this package. | ai |
Versions (showing 7 of 7)
| Version | Deps | Published |
|---|---|---|
| 5.3.0 | 5 / 7 | |
| 5.2.2 | 5 / 6 | |
| 5.2.1 | 5 / 6 | |
| 5.2.0 | 5 / 6 | |
| 5.1.0 | 5 / 6 | |
| 5.0.1 | 5 / 6 | |
| 5.0.0 | 5 / 6 |
v5.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.2.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.2.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.