@expo/prebuild-config
Get the prebuild config
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 |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): brentvatne is a core Expo team member with a 10+ year track record; publisher rotation within the Expo org is expected and not a security concern for this package. | ai |
Versions (showing 88 of 188)
| Version | Deps | Published |
|---|---|---|
| 8.0.2 | 11 / 3 | |
| 8.0.1 | 11 / 3 | |
| 8.0.0 | 11 / 3 | |
| 7.0.9 | 11 / 3 | |
| 7.0.8 | 11 / 3 | |
| 7.0.7 | 11 / 3 | |
| 7.0.6 | 11 / 3 | |
| 7.0.5 | 11 / 3 | |
| 7.0.4 | 11 / 3 | |
| 7.0.3 | 11 / 3 | |
| 7.0.2 | 11 / 3 | |
| 7.0.1 | 11 / 3 | |
| 7.0.0 | 11 / 3 | |
| 6.8.1 | 10 / 3 | |
| 6.8.0 | 10 / 3 | |
| 6.7.4 | 10 / 3 | |
| 6.7.3 | 10 / 3 | |
| 6.7.2 | 10 / 3 | |
| 6.7.1 | 10 / 2 | |
| 6.7.0 | 10 / 2 | |
| 6.6.0 | 10 / 2 | |
| 6.5.0 | 10 / 2 | |
| 6.4.1 | 10 / 2 | |
| 6.4.0 | 10 / 2 | |
| 6.3.0 | 10 / 2 | |
| 6.2.6 | 10 / 2 | |
| 6.2.5 | 10 / 2 | |
| 6.2.4 | 10 / 2 | |
| 6.2.3 | 10 / 2 | |
| 6.2.2 | 10 / 2 | |
| 6.2.1 | 10 / 2 | |
| 6.2.0 | 10 / 2 | |
| 6.1.0 | 10 / 2 | |
| 6.0.2 | 10 / 2 | |
| 6.0.1 | 10 / 2 | |
| 6.0.0 | 10 / 2 | |
| 5.0.7 | 10 / 2 | |
| 5.0.6 | 10 / 2 | |
| 5.0.5 | 10 / 2 | |
| 5.0.4 | 10 / 2 | |
| 5.0.3 | 10 / 2 | |
| 5.0.2 | 10 / 2 | |
| 5.0.1 | 10 / 2 | |
| 5.0.0 | 10 / 2 | |
| 4.0.4 | 11 / 2 | |
| 4.0.3 | 11 / 2 | |
| 4.0.2 | 11 / 2 | |
| 4.0.1 | 11 / 2 | |
| 4.0.0 | 11 / 2 | |
| 3.1.6 | 11 / 2 | |
| 3.1.5 | 11 / 2 | |
| 3.1.4 | 11 / 2 | |
| 3.1.3 | 11 / 2 | |
| 3.1.2 | 11 / 2 | |
| 3.1.1 | 11 / 2 | |
| 3.1.0 | 11 / 2 | |
| 3.0.18 | 11 / 2 | |
| 3.0.17 | 11 / 2 | |
| 3.0.16 | 11 / 2 | |
| 3.0.15 | 11 / 2 | |
| 3.0.14 | 11 / 2 | |
| 3.0.13 | 11 / 2 | |
| 3.0.12 | 11 / 2 | |
| 3.0.11 | 10 / 2 | |
| 3.0.10 | 10 / 2 | |
| 3.0.9 | 10 / 2 | |
| 3.0.8 | 10 / 2 | |
| 3.0.7 | 9 / 1 | |
| 3.0.6 | 9 / 1 | |
| 3.0.4 | 9 / 1 | |
| 3.0.3 | 9 / 1 | |
| 3.0.2 | 9 / 1 | |
| 3.0.0 | 9 / 1 | |
| 2.1.0 | 8 / 1 | |
| 2.0.8 | 8 / 1 | |
| 2.0.7 | 8 / 1 | |
| 2.0.6 | 8 / 1 | |
| 2.0.5 | 8 / 1 | |
| 2.0.4 | 8 / 1 | |
| 2.0.3 | 8 / 1 | |
| 2.0.2 | 8 / 1 | |
| 2.0.1 | 8 / 1 | |
| 2.0.0 | 8 / 1 | |
| 1.0.5 | 9 / 1 | |
| 1.0.4 | 9 / 1 | |
| 1.0.3 | 8 / 0 | |
| 1.0.2 | 8 / 0 | |
| 1.0.1 | 8 / 0 |
v8.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.0.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.0.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.0.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.0.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.0.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.0.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.