react-native-toast-message
6
Versions
—
License
No
Install Scripts
Verified
Provenance
Supply chain provenance
Status for the latest visible version.
SLSA provenance attestation
npm registry signatures
gitHead linked
Maintainers
calintamas
Keywords
react-nativetoast
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Legit manual→GitHub Actions CI/CD transition with SLSA provenance; not a takeover. | ai |
Versions (showing 6 of 6)
| Version | Deps | Published |
|---|---|---|
| 2.4.0 | 0 / 16 | |
| 2.3.3 | 0 / 17 | |
| 2.3.2 | 0 / 17 | |
| 2.3.1 | 0 / 17 | |
| 2.3.0 | 0 / 17 | |
| 2.2.1 | 0 / 17 |
v2.4.0
2 findings
HIGH
Publisher changed: calintamas → GitHub Actions (on 2026-07-07)
provenance
This version was published by a different npm account than previous versions on 2026-07-07. This could indicate a legitimate maintainer transition or an account compromise.
INFO
Has SLSA provenance attestation
provenance
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.3.0
1 finding
LOW
No provenance attestation
provenance
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.1
1 finding
LOW
No provenance attestation
provenance
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.