@react-email/markdown
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Keywords
Versions (showing 9 of 9)
| Version | Deps | Published |
|---|---|---|
| 0.0.18 | 1 / 3 | |
| 0.0.17 | 1 / 3 | |
| 0.0.16 | 1 / 3 | |
| 0.0.15 | 1 / 3 | |
| 0.0.14 | 1 / 4 | |
| 0.0.13 | 1 / 4 | |
| 0.0.12 | 1 / 4 | |
| 0.0.11 | 1 / 5 | |
| 0.0.10 | 1 / 5 |
v0.0.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.