@react-email/text
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| typosquat | typosquat.levenshtein:next | AI (typosquat): Scoped @react-email/text is not a typosquat of 'next'; stable FP for this package. | ai | |
| typosquat | typosquat.levenshtein:nuxt | AI (typosquat): Scoped @react-email/text is not a typosquat of 'nuxt'; stable FP for this package. | ai | |
| typosquat | typosquat.levenshtein:jest | AI (typosquat): Scoped @react-email/text is not a typosquat of 'jest'; stable FP for this package. | ai |
Versions (showing 5 of 5)
| Version | Deps | Published |
|---|---|---|
| 0.1.6 | 0 / 3 | |
| 0.1.5 | 0 / 3 | |
| 0.1.4 | 0 / 3 | |
| 0.1.3 | 0 / 3 | |
| 0.1.2 | 0 / 3 |
v0.1.6
2 findingsPackage name '@react-email/text' is 1 edit(s) away from popular package 'next'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.5
2 findingsPackage name '@react-email/text' is 1 edit(s) away from popular package 'next'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.4
2 findingsPackage name '@react-email/text' is 1 edit(s) away from popular package 'next'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.3
2 findingsPackage name '@react-email/text' is 1 edit(s) away from popular package 'next'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.2
2 findingsPackage name '@react-email/text' is 1 edit(s) away from popular package 'next'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.