mjml-image
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:mjml-core | AI (dependencies): mjml-core is a sibling package in the official MJML monorepo; its use as a dependency in mjml-image is expected and stable across all versions. | ai | |
| provenance | no-provenance | AI (provenance): MJML packages have historically not published Sigstore provenance; this is consistent across the entire package family and not a risk indicator. | ai |
Versions (showing 11 of 11)
| Version | Deps | Published |
|---|---|---|
| 5.3.0 | 3 / 2 | |
| 5.2.2 | 3 / 2 | |
| 5.2.1 | 3 / 2 | |
| 5.2.0 | 3 / 2 | |
| 5.1.0 | 3 / 2 | |
| 5.0.1 | 3 / 2 | |
| 5.0.0 | 3 / 2 | |
| 4.18.0 | 3 / 2 | |
| 4.17.2 | 3 / 2 | |
| 4.17.1 | 3 / 2 | |
| 4.17.0 | 3 / 2 |
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.
v4.18.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.17.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.17.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.
v4.17.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.