@react-native/babel-preset
Babel preset for React Native applications
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@babel/core | AI (phantom-deps): Babel presets load plugins by convention; @babel/core is a framework-scoped dependency loaded dynamically, not directly imported. | ai | |
| phantom-deps | phantom-dep:@babel/template | AI (phantom-deps): Babel presets load plugins by convention; @babel/template is a framework-scoped dependency loaded dynamically, not directly imported. | ai | |
| bogus-package | bogus-package | AI (bogus-package): False positive: react-native-bot is Facebook's official React Native automation account, not a spam publisher. Repository confirms legitimacy. | ai |
Versions (showing 51 of 101)
| Version | Deps | Published |
|---|---|---|
| 0.85.3 | 33 / 0 | |
| 0.85.2 | 33 / 0 | |
| 0.85.1 | 33 / 0 | |
| 0.85.0 | 33 / 0 | |
| 0.84.1 | 33 / 0 | |
| 0.84.0 | 33 / 0 | |
| 0.83.9 | 45 / 0 | |
| 0.83.8 | 45 / 0 | |
| 0.83.7 | 45 / 0 | |
| 0.83.6 | 45 / 0 | |
| 0.83.5 | 45 / 0 | |
| 0.83.4 | 45 / 0 | |
| 0.83.3 | 45 / 0 | |
| 0.83.2 | 45 / 0 | |
| 0.83.1 | 45 / 0 | |
| 0.83.0 | 45 / 0 | |
| 0.82.1 | 45 / 0 | |
| 0.82.0 | 45 / 0 | |
| 0.81.6 | 45 / 0 | |
| 0.81.5 | 45 / 0 | |
| 0.81.4 | 45 / 0 | |
| 0.81.3 | 45 / 0 | |
| 0.81.2 | 45 / 0 | |
| 0.81.1 | 45 / 0 | |
| 0.81.0 | 45 / 0 | |
| 0.80.3 | 45 / 0 | |
| 0.80.2 | 45 / 0 | |
| 0.80.1 | 45 / 0 | |
| 0.80.0 | 45 / 0 | |
| 0.79.7 | 45 / 0 | |
| 0.79.6 | 45 / 0 | |
| 0.79.5 | 45 / 0 | |
| 0.79.4 | 45 / 0 | |
| 0.79.3 | 45 / 0 | |
| 0.79.2 | 45 / 0 | |
| 0.79.1 | 45 / 0 | |
| 0.79.0 | 45 / 0 | |
| 0.78.3 | 45 / 0 | |
| 0.78.2 | 45 / 0 | |
| 0.78.1 | 45 / 0 | |
| 0.78.0 | 45 / 0 | |
| 0.77.3 | 45 / 0 | |
| 0.77.2 | 45 / 0 | |
| 0.77.1 | 45 / 0 | |
| 0.77.0 | 45 / 0 | |
| 0.76.9 | 45 / 0 | |
| 0.76.8 | 45 / 0 | |
| 0.76.7 | 45 / 0 | |
| 0.76.6 | 45 / 0 | |
| 0.76.5 | 45 / 0 | |
| 0.76.4 | 45 / 0 |
v0.85.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.85.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.85.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.85.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.84.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.84.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.83.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.83.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.83.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.83.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.83.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.83.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.83.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.83.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.83.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.83.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.82.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.82.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.81.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.81.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.81.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.81.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.81.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.81.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.81.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.80.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.80.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.80.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.80.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.79.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.79.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.79.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.79.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.79.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.79.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.79.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.79.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.78.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.78.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.78.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.78.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.77.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.77.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.77.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.77.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.76.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.76.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.76.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.76.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.76.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.76.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.