@expo/babel-preset-cli
The Babel preset for Expo CLI packages
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/preset-env | AI (phantom-deps): Babel preset convention: dependencies are loaded by Babel's plugin/preset discovery, not direct imports. | ai | |
| phantom-deps | phantom-dep:@babel/preset-typescript | AI (phantom-deps): Babel preset convention: dependencies are loaded by Babel's plugin/preset discovery, not direct imports. | ai | |
| phantom-deps | phantom-dep:@babel/plugin-proposal-class-properties | AI (phantom-deps): Babel preset convention: dependencies are loaded by Babel's plugin/preset discovery, not direct imports. | ai | |
| provenance | publisher-changed | AI (provenance): Publisher change from evanbacon to keith-kurak reflects a routine Expo team transition; both are known Expo org members with strong track records. | ai | |
| phantom-deps | phantom-dep:@babel/core | AI (phantom-deps): @babel/core is a declared dependency of a Babel preset package and is loaded by convention; phantom-dep finding is a stable false positive for this package. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): New maintainers (marklawlor, gabrieldonadel, simek) are known Expo org contributors; addition reflects normal team growth within the Expo organization. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Removal of tcdavis is consistent with normal Expo team roster changes; no evidence of hostile takeover. | ai |
Versions (showing 33 of 33)
| Version | Deps | Published |
|---|---|---|
| 0.3.1 | 9 / 1 | |
| 0.3.0 | 9 / 1 | |
| 0.2.25 | 9 / 1 | |
| 0.2.24 | 9 / 1 | |
| 0.2.23 | 9 / 1 | |
| 0.2.22 | 9 / 1 | |
| 0.2.21 | 9 / 1 | |
| 0.2.20 | 8 / 1 | |
| 0.2.19 | 8 / 1 | |
| 0.2.18 | 7 / 1 | |
| 0.2.17 | 7 / 1 | |
| 0.2.16 | 7 / 1 | |
| 0.2.15 | 7 / 1 | |
| 0.2.14 | 8 / 1 | |
| 0.2.13 | 8 / 1 | |
| 0.2.12 | 8 / 1 | |
| 0.2.11 | 8 / 1 | |
| 0.2.10 | 8 / 1 | |
| 0.2.9 | 8 / 1 | |
| 0.2.8 | 8 / 0 | |
| 0.2.7 | 8 / 0 | |
| 0.2.6 | 8 / 0 | |
| 0.2.5 | 8 / 0 | |
| 0.2.4 | 8 / 0 | |
| 0.2.3 | 7 / 0 | |
| 0.2.2 | 6 / 0 | |
| 0.2.1 | 5 / 0 | |
| 0.2.0 | 5 / 0 | |
| 0.1.5 | 4 / 0 | |
| 0.1.4 | 4 / 0 | |
| 0.1.3 | 4 / 0 | |
| 0.1.2 | 4 / 0 | |
| 0.1.1 | 4 / 0 |
v0.3.1
2 findingsThis version was published by a different npm account than previous versions on 2023-06-07. 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.3.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2023-01-27. This could indicate a legitimate maintainer transition or an account compromise.
v0.2.25
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2023-01-05. This could indicate a legitimate maintainer transition or an account compromise.
v0.2.24
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.23
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.22
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.21
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.18
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2020-09-17. This could indicate a legitimate maintainer transition or an account compromise.
v0.2.17
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2020-07-30. This could indicate a legitimate maintainer transition or an account compromise.
v0.2.16
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2020-05-26. This could indicate a legitimate maintainer transition or an account compromise.
v0.2.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.13
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2020-05-12. This could indicate a legitimate maintainer transition or an account compromise.
v0.2.12
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2020-05-11. This could indicate a legitimate maintainer transition or an account compromise.
v0.2.11
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2020-04-29. This could indicate a legitimate maintainer transition or an account compromise.
v0.2.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.6
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2020-03-07. This could indicate a legitimate maintainer transition or an account compromise.
v0.2.5
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2020-01-14. This could indicate a legitimate maintainer transition or an account compromise.
v0.2.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.2
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2019-12-06. This could indicate a legitimate maintainer transition or an account compromise.
v0.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2019-08-06. This could indicate a legitimate maintainer transition or an account compromise.
v0.1.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.4
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2019-07-19. This could indicate a legitimate maintainer transition or an account compromise.
v0.1.3
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2019-07-05. This could indicate a legitimate maintainer transition or an account compromise.
v0.1.2
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2019-06-24. This could indicate a legitimate maintainer transition or an account compromise.
v0.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.