metro-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 |
|---|---|---|---|---|
| publish-pattern | new-deps-added | AI (publish-pattern): New deps are standard @babel scope plugins consistent with this preset's purpose; metro-bot is a trusted publisher with strong track record. | ai | |
| provenance | no-provenance | AI (provenance): Established Facebook/Meta package published via metro-bot; lack of Sigstore provenance is a known gap for this publisher, not a security risk. | ai | |
| provenance | publisher-changed | AI (provenance): Transition from cpojer to metro-bot is a known legitimate change within Meta's Metro monorepo publishing automation. | ai | |
| phantom-deps | phantom-dep:@babel/core | AI (phantom-deps): @babel/core is a peer dependency and framework convention for Babel presets; not directly imported but required at runtime. | ai | |
| semgrep | semgrep:dynamic-require | AI (semgrep): Dynamic require in resolvePlugins.js is intentional Babel preset plugin resolution by string name with a known prefix — standard pattern for Babel presets, not a security risk. | ai | |
| phantom-deps | phantom-dep:@babel/template | AI (phantom-deps): @babel/template is explicitly listed as a direct dependency in package.json; this is a stable false positive for this package. | ai |
Versions (showing 51 of 98)
| Version | Deps | Published |
|---|---|---|
| 0.77.0 | 39 / 0 | |
| 0.76.9 | 39 / 0 | |
| 0.76.8 | 39 / 0 | |
| 0.76.7 | 39 / 0 | |
| 0.76.6 | 39 / 0 | |
| 0.76.5 | 39 / 0 | |
| 0.76.4 | 39 / 0 | |
| 0.76.3 | 39 / 0 | |
| 0.76.2 | 39 / 0 | |
| 0.76.1 | 39 / 0 | |
| 0.76.0 | 39 / 0 | |
| 0.75.1 | 39 / 0 | |
| 0.75.0 | 38 / 0 | |
| 0.74.1 | 38 / 0 | |
| 0.74.0 | 37 / 0 | |
| 0.73.10 | 38 / 0 | |
| 0.73.9 | 38 / 0 | |
| 0.73.8 | 38 / 0 | |
| 0.73.7 | 38 / 0 | |
| 0.73.6 | 38 / 0 | |
| 0.73.5 | 38 / 0 | |
| 0.73.4 | 38 / 0 | |
| 0.73.3 | 38 / 0 | |
| 0.73.2 | 38 / 0 | |
| 0.73.1 | 38 / 0 | |
| 0.73.0 | 38 / 0 | |
| 0.72.4 | 39 / 0 | |
| 0.72.3 | 39 / 0 | |
| 0.72.2 | 39 / 0 | |
| 0.72.1 | 39 / 0 | |
| 0.72.0 | 39 / 0 | |
| 0.71.3 | 39 / 0 | |
| 0.71.2 | 39 / 0 | |
| 0.71.1 | 39 / 0 | |
| 0.71.0 | 39 / 0 | |
| 0.70.3 | 39 / 0 | |
| 0.70.2 | 39 / 0 | |
| 0.70.1 | 39 / 0 | |
| 0.70.0 | 38 / 0 | |
| 0.69.1 | 40 / 0 | |
| 0.69.0 | 40 / 0 | |
| 0.68.0 | 41 / 0 | |
| 0.67.0 | 40 / 0 | |
| 0.66.2 | 40 / 0 | |
| 0.66.1 | 40 / 0 | |
| 0.66.0 | 40 / 0 | |
| 0.65.2 | 40 / 0 | |
| 0.65.1 | 40 / 0 | |
| 0.65.0 | 39 / 0 | |
| 0.64.0 | 39 / 0 | |
| 0.63.0 | 39 / 0 |
v0.77.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.76.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.76.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.76.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.76.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.76.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.76.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.76.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.76.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.76.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.76.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.75.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.75.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.74.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.74.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.73.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.73.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.73.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.73.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.73.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.73.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.73.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.73.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.73.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.73.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.73.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.72.4
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: metro-bot.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.72.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.72.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.72.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.72.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.71.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.71.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.71.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.71.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.70.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.70.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.70.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.70.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.69.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.69.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.68.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.67.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.66.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.66.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.66.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.65.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.65.1
2 findingsThis version was published by a different npm account than previous versions on 2021-02-15. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.65.0
2 findingsThis version was published by a different npm account than previous versions on 2021-01-28. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.64.0
2 findingsThis version was published by a different npm account than previous versions on 2020-11-05. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.63.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.