react-native-edge-to-edge
Effortlessly enable edge-to-edge display in React Native
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 |
|---|---|---|---|---|
| npm-metadata | suspicious-initial-version | AI (npm-metadata): 0.0.0 is a namespace reservation placeholder by a well-established publisher (brentvatne) with 746k weekly downloads on the real versions. Not indicative of malicious intent. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Placeholder 0.0.0 version by a trusted publisher; the package has 29 real versions and 746k weekly downloads. Bogus signals reflect the placeholder, not spam/malware. | ai |
Versions (showing 27 of 27)
| Version | Deps | Published |
|---|---|---|
| 1.8.1 | 0 / 10 | |
| 1.8.0 | 0 / 10 | |
| 1.7.0 | 0 / 10 | |
| 1.6.2 | 0 / 10 | |
| 1.6.1 | 0 / 10 | |
| 1.6.0 | 0 / 10 | |
| 1.5.1 | 0 / 10 | |
| 1.5.0 | 0 / 10 | |
| 1.4.3 | 0 / 10 | |
| 1.4.2 | 0 / 10 | |
| 1.4.1 | 0 / 10 | |
| 1.4.0 | 0 / 10 | |
| 1.3.1 | 0 / 10 | |
| 1.3.0 | 0 / 10 | |
| 1.2.0 | 0 / 10 | |
| 1.1.3 | 0 / 10 | |
| 1.1.2 | 0 / 10 | |
| 1.1.1 | 0 / 10 | |
| 1.1.0 | 0 / 10 | |
| 1.0.1 | 0 / 10 | |
| 1.0.0 | 0 / 10 | |
| 0.2.1 | 0 / 10 | |
| 0.2.0 | 0 / 10 | |
| 0.1.2 | 0 / 10 | |
| 0.1.1 | 0 / 10 | |
| 0.1.0 | 0 / 10 | |
| 0.0.0 | 0 / 0 |
v1.8.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.