← Home

react-native-is-edge-to-edge

npm Repository Homepage

Detect react-native-edge-to-edge package install

17
Versions
MIT
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

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

brentvatnezoontek

Keywords

reactreact-nativeedge-to-edgestatus-barnavigation-barsystem-barsystem-bars

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
npm-metadata suspicious-initial-version AI (npm-metadata): 0.0.0 is a known stub/placeholder pattern for this package in the React Native/Expo ecosystem; not indicative of malice given 4.8M weekly downloads and trusted publisher. ai
bogus-package bogus-package AI (bogus-package): Package is a well-known stub/shim with 4.8M weekly downloads and a highly trusted publisher (brentvatne). Sparse metadata is intentional for this placeholder pattern. ai
npm-metadata no-description AI (npm-metadata): Intentional stub package; missing description is consistent with its placeholder role in the ecosystem. ai
provenance publisher-changed AI (provenance): Legitimate transfer from brentvatne (Expo/RN core) to zoontek, the author of the parent react-native-edge-to-edge project. Repo URL confirms ownership. ai
maintainer-change maintainer-added AI (maintainer-change): zoontek is the author of react-native-edge-to-edge; this package is part of that project. Transfer is legitimate. ai

Versions (showing 17 of 17)

Version Deps Published
1.3.1 0 / 5
1.3.0 0 / 5
1.2.1 0 / 5
1.2.0 0 / 5
1.1.7 0 / 5
1.1.6 0 / 5
1.1.5 0 / 5
1.1.4 0 / 5
1.1.3 0 / 5
1.1.2 0 / 5
1.1.1 0 / 5
1.1.0 0 / 5
1.0.0 0 / 4
0.1.2 0 / 4
0.1.1 0 / 4
0.1.0 0 / 4
0.0.0 0 / 0

v1.3.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.2.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.2.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.1.7

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.1.6

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.1.5

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.1.4

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.1.3

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.1.2

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.1.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.1.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.1.2

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.1.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.1.0

2 findings
HIGH Publisher changed: brentvatne → zoontek (on 2024-10-11) provenance

This version was published by a different npm account than previous versions on 2024-10-11. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.0.0

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.