← Home

babel-preset-expo

npm Repository Homepage

The Babel preset for Expo projects

88
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

idebrentvatneevanbaconexpoadminexponentbycedrickudochienalanhughestsapetaexpo-botphilplwschurman

Keywords

babelbabel-presetexpoexpo-webreact-nativereact-native-webmetrowebpack

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): alanhughes is a known Expo team member (813 days, 5834 approved packages). The change from expo-bot to a human publisher is a normal operational pattern for the Expo monorepo. ai
phantom-deps phantom-dep:resolve-from AI (phantom-deps): resolve-from is a declared runtime dependency used by convention in this Babel preset; not directly imported but legitimately used. ai
phantom-deps phantom-dep:@babel/plugin-transform-export-namespace-from AI (phantom-deps): Babel plugins in presets are loaded by string reference, not direct import. This is standard Babel preset architecture. ai

Versions (showing 88 of 188)

Hide prereleases
Version Deps Published
11.0.4 9 / 3
11.0.3 9 / 3
11.0.2 9 / 3
11.0.1 9 / 3
11.0.0 9 / 3
10.0.2 9 / 3
10.0.1 9 / 3
10.0.0 9 / 3
9.9.0 9 / 2
9.8.0 8 / 2
9.7.0 8 / 2
9.6.2 8 / 2
9.6.1 8 / 2
9.6.0 8 / 2
9.5.2 8 / 2
9.5.1 8 / 2
9.5.0 8 / 2
9.4.1 7 / 2
9.4.0 7 / 2
9.3.2 7 / 2
9.3.1 7 / 2
9.3.0 7 / 2
9.2.2 7 / 2
9.2.1 6 / 2
9.2.0 6 / 2
9.1.0 6 / 2
9.0.2 6 / 2
9.0.1 6 / 2
9.0.0 6 / 2
8.5.1 6 / 2
8.5.0 6 / 2
8.4.1 5 / 2
8.4.0 5 / 2
8.3.0 5 / 2
8.2.3 5 / 2
8.2.2 5 / 2
8.2.1 5 / 2
8.2.0 5 / 2
8.1.1 5 / 2
8.1.0 5 / 2
8.0.0 5 / 2
7.1.0 7 / 1
7.0.0 7 / 1
6.0.0 7 / 1
5.2.0 7 / 1
5.1.1 6 / 1
5.1.0 6 / 1
5.0.0 3 / 2
4.0.0 5 / 2
3.0.0 5 / 2
2.0.0 3 / 0
1.0.1 3 / 0
1.0.0 3 / 0
56.0.0-canary-20260420-2ac87c0 22 / 12
56.0.0-canary-20260417-141204f 22 / 12
56.0.0-canary-20260414-e3dbafd 22 / 12
56.0.0-canary-20260409-6fc2991 22 / 11
56.0.0-canary-20260402-87c5ce2 23 / 6
56.0.0-canary-20260305-5163746 23 / 6
56.0.0-canary-20260212-4f61309 23 / 6
55.0.14-canary-20260402-9da566b 23 / 6
55.0.14-canary-20260401-5e87ef7 23 / 6
55.0.14-canary-20260328-bdc6273 23 / 6
55.0.14-canary-20260328-2049187 23 / 6
55.0.14-canary-20260327-0789fbc 23 / 6
55.0.3-canary-20260128-67ce8d5 22 / 6
55.0.0-canary-20260223-05214f1 23 / 6
54.1.0-canary-20260121-a63c0dd 22 / 6
54.1.0-canary-20260120-bb71700 22 / 6
54.1.0-canary-20260119-70f7c28 22 / 6
54.1.0-canary-20260114-d8e19f5 22 / 6
54.1.0-canary-20260105-6b962e6 22 / 6
54.1.0-canary-20251230-fc48ddc 22 / 6
54.1.0-canary-20251223-b83b31e 22 / 6
54.1.0-canary-20251216-6e1f9a7 22 / 6
54.1.0-canary-20251216-3f01dbf 22 / 6
54.1.0-canary-20251212-acb11f2 22 / 6
54.1.0-canary-20251211-7da85ea 22 / 6
54.1.0-canary-20251210-1f163e3 22 / 6
54.1.0-canary-20251206-615dec1 22 / 6
54.1.0-canary-20251205-a1dedc6 22 / 6
54.1.0-canary-20251205-756eb7a 22 / 6
54.1.0-canary-20251127-587bc53 22 / 6
54.1.0-canary-20251120-e46b3cc 22 / 6
54.1.0-canary-20251119-961a032 22 / 6
54.1.0-canary-20251118-8f7ee64 22 / 6
54.0.10-canary-20260119-17896bf 22 / 6
54.0.7-canary-20251031-b135dff 22 / 6

v11.0.4

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.

v11.0.3

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.

v11.0.2

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.

v11.0.1

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.