@react-email/row
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| typosquat | typosquat.levenshtein:koa | AI (typosquat): Scoped @react-email package; 'row' suffix match to 'koa' is a false positive. | ai | |
| typosquat | typosquat.levenshtein:got | AI (typosquat): Scoped @react-email package; 'row' suffix match to 'got' is a false positive. | ai | |
| typosquat | typosquat.levenshtein:joi | AI (typosquat): Scoped @react-email package; 'row' suffix match to 'joi' is a false positive. | ai | |
| typosquat | typosquat.levenshtein:zod | AI (typosquat): Scoped @react-email package; 'row' suffix match to 'zod' is a false positive. | ai |
Versions (showing 6 of 6)
| Version | Deps | Published |
|---|---|---|
| 0.0.13 | 0 / 3 | |
| 0.0.12 | 0 / 4 | |
| 0.0.11 | 0 / 4 | |
| 0.0.10 | 0 / 4 | |
| 0.0.9 | 0 / 5 | |
| 0.0.8 | 0 / 5 |
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. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.