@m5kdev/email
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | missing-githead | AI (provenance): No diff vs last approved version; consistent with automated monorepo release pipeline. | ai | |
| publish-pattern | rapid-publish | AI (publish-pattern): 100 versions/127 days indicates routine automated releases, not anomalous. | ai | |
| phantom-deps | phantom-dep:react-dom | AI (phantom-deps): react-dom is a declared runtime dependency; phantom-dep fires because it's not directly imported in source, but it's a peer/runtime requirement for React email rendering. | ai |
Versions (showing 100 of 122)
| Version | Deps | Published |
|---|---|---|
| 0.31.11 | 3 / 8 | |
| 0.31.10 | 3 / 8 | |
| 0.31.9 | 3 / 8 | |
| 0.31.7 | 3 / 8 | |
| 0.31.6 | 3 / 8 | |
| 0.31.5 | 3 / 8 | |
| 0.31.4 | 3 / 8 | |
| 0.31.2 | 3 / 8 | |
| 0.31.1 | 3 / 8 | |
| 0.31.0 | 3 / 8 | |
| 0.30.0 | 3 / 8 | |
| 0.29.0 | 3 / 8 | |
| 0.28.13 | 3 / 8 | |
| 0.28.12 | 3 / 8 | |
| 0.28.11 | 3 / 8 | |
| 0.28.9 | 3 / 8 | |
| 0.28.8 | 3 / 8 | |
| 0.28.3 | 3 / 8 | |
| 0.28.2 | 3 / 8 | |
| 0.28.1 | 3 / 8 | |
| 0.28.0 | 3 / 8 | |
| 0.27.2 | 3 / 8 | |
| 0.27.1 | 3 / 8 | |
| 0.27.0 | 3 / 8 | |
| 0.26.6 | 3 / 8 | |
| 0.26.5 | 3 / 8 | |
| 0.26.4 | 3 / 8 | |
| 0.26.3 | 3 / 8 | |
| 0.26.2 | 3 / 8 | |
| 0.26.1 | 3 / 8 | |
| 0.25.3 | 3 / 8 | |
| 0.25.2 | 3 / 8 | |
| 0.25.1 | 3 / 8 | |
| 0.25.0 | 3 / 8 | |
| 0.23.0 | 3 / 8 | |
| 0.21.9 | 3 / 8 | |
| 0.21.7 | 3 / 8 | |
| 0.21.4 | 3 / 8 | |
| 0.21.3 | 3 / 8 | |
| 0.21.2 | 3 / 8 | |
| 0.21.1 | 3 / 8 | |
| 0.21.0 | 3 / 8 | |
| 0.20.51 | 3 / 8 | |
| 0.20.49 | 3 / 8 | |
| 0.20.48 | 3 / 8 | |
| 0.20.38 | 3 / 8 | |
| 0.20.34 | 3 / 8 | |
| 0.20.32 | 3 / 8 | |
| 0.20.8 | 3 / 8 | |
| 0.20.5 | 3 / 8 | |
| 0.20.0 | 3 / 8 | |
| 0.19.3 | 3 / 8 | |
| 0.19.2 | 3 / 8 | |
| 0.19.1 | 3 / 8 | |
| 0.19.0 | 3 / 8 | |
| 0.18.0 | 3 / 8 | |
| 0.17.7 | 3 / 8 | |
| 0.17.6 | 3 / 8 | |
| 0.17.5 | 3 / 8 | |
| 0.17.4 | 3 / 8 | |
| 0.17.3 | 3 / 8 | |
| 0.17.2 | 3 / 8 | |
| 0.17.1 | 3 / 8 | |
| 0.17.0 | 3 / 8 | |
| 0.16.9 | 3 / 8 | |
| 0.16.8 | 3 / 8 | |
| 0.16.7 | 3 / 8 | |
| 0.16.6 | 3 / 8 | |
| 0.16.5 | 3 / 8 | |
| 0.16.4 | 3 / 8 | |
| 0.16.3 | 3 / 8 | |
| 0.16.2 | 3 / 8 | |
| 0.16.1 | 3 / 8 | |
| 0.16.0 | 3 / 8 | |
| 0.15.3 | 3 / 8 | |
| 0.15.2 | 3 / 8 | |
| 0.15.1 | 3 / 8 | |
| 0.15.0 | 3 / 8 | |
| 0.14.0 | 3 / 8 | |
| 0.13.1 | 3 / 8 | |
| 0.13.0 | 3 / 8 | |
| 0.12.0 | 3 / 8 | |
| 0.11.0 | 3 / 8 | |
| 0.10.1 | 3 / 8 | |
| 0.10.0 | 3 / 8 | |
| 0.9.8 | 3 / 8 | |
| 0.9.7 | 3 / 8 | |
| 0.9.6 | 3 / 8 | |
| 0.9.5 | 3 / 8 | |
| 0.9.4 | 3 / 8 | |
| 0.9.3 | 3 / 8 | |
| 0.9.2 | 3 / 8 | |
| 0.9.1 | 3 / 8 | |
| 0.9.0 | 3 / 8 | |
| 0.8.11 | 3 / 8 | |
| 0.8.10 | 3 / 8 | |
| 0.8.9 | 3 / 8 | |
| 0.8.8 | 3 / 8 | |
| 0.8.7 | 3 / 8 | |
| 0.8.6 | 3 / 8 |
v0.31.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.31.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.31.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.31.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.31.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.31.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.31.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.31.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.31.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.31.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.30.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.29.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.28.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.28.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.28.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.28.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.28.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.28.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.28.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.28.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.28.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.27.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.27.1
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: reion.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.27.0
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: reion.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.26.6
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: reion.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.26.5
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: reion.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.26.4
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: reion.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.26.3
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: reion.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.26.2
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: reion.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.26.1
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: reion.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.25.3
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: reion.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.25.2
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: reion.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.25.1
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: reion.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.25.0
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: reion.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.23.0
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: reion.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.21.9
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: reion.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.21.7
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: reion.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.21.4
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: reion.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.21.3
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: reion.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.21.2
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: reion.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.