← Home

expo

npm Repository Homepage
39
Versions
—
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

expo

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
source-diff net-exec-file:src/async-require/__tests__/asyncRequireModule.test.ts AI (source-diff): Test file using new Function() to simulate Metro module evaluation; not production code, not malware. ai
semgrep semgrep:new-function-constructor AI (semgrep): Same test file pattern — controlled Metro simulation in unit tests, stable false positive for this package. ai
provenance publisher-changed AI (provenance): alanhughes is an established Expo org publisher with 5888 approved packages; routine maintainer rotation. ai
source-diff net-exec-file:src/async-require/fetchThenEvalJs.ts AI (source-diff): Documented Metro split-bundle loader; eval(body) fetches from local dev server, not arbitrary remote URLs. ai
semgrep semgrep:eval-usage AI (semgrep): eval() in fetchThenEvalJs is intentional Metro async-require pattern; stable across expo versions. ai
phantom-deps phantom-dep:@expo/vector-icons AI (phantom-deps): Expo monorepo pattern; stable false positive. ai
phantom-deps phantom-dep:@expo/cli AI (phantom-deps): Expo monorepo pattern; CLI is referenced via config/bin, not direct import. ai
phantom-deps phantom-dep:react-native-edge-to-edge AI (phantom-deps): Platform-specific binary package; not directly imported by design. ai
phantom-deps phantom-dep:expo-font AI (phantom-deps): Framework-level dep loaded by convention, not direct import. ai
phantom-deps phantom-dep:@babel/runtime AI (phantom-deps): Framework-scoped transitive dep; stable false positive for this package. ai
phantom-deps phantom-dep:expo-file-system AI (phantom-deps): Expo monorepo pattern; loaded by convention. ai
phantom-deps phantom-dep:babel-preset-expo AI (phantom-deps): Build tooling dep referenced in config, not imported directly. ai

Versions (showing 39 of 39)

Version Deps Published
56.0.8 23 / 11
56.0.7 23 / 11
56.0.6 23 / 11
56.0.5 23 / 11
56.0.4 23 / 11
56.0.3 23 / 11
56.0.2 23 / 11
56.0.1 23 / 11
56.0.0 23 / 11
55.0.26 23 / 10
55.0.25 23 / 10
55.0.24 23 / 10
55.0.23 23 / 10
55.0.22 23 / 10
55.0.21 23 / 10
55.0.20 23 / 10
55.0.19 23 / 10
55.0.18 23 / 10
55.0.17 23 / 10
55.0.10 23 / 10
55.0.9 23 / 10
55.0.0 23 / 10
54.0.35 21 / 8
54.0.34 21 / 8
54.0.33 21 / 8
54.0.32 21 / 8
54.0.31 21 / 8
54.0.30 21 / 8
54.0.29 21 / 8
54.0.28 21 / 8
54.0.27 21 / 8
54.0.26 21 / 8
54.0.25 21 / 8
54.0.24 21 / 8
54.0.23 21 / 8
53.0.25 17 / 9
53.0.24 17 / 9
53.0.9 17 / 9
52.0.48 18 / 6

v56.0.8

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v56.0.7

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v56.0.6

2 findings
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Publisher changed: alanhughes → kudochien (on 2026-05-28, known maintainer) provenance

This version was published by a different npm account (kudochien) than the most recent previously approved version (alanhughes) on 2026-05-28, but kudochien is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v56.0.5

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v56.0.4

2 findings
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Publisher changed: brentvatne → alanhughes (on 2026-05-23, known maintainer) provenance

This version was published by a different npm account (alanhughes) than the most recent previously approved version (brentvatne) on 2026-05-23, but alanhughes is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v56.0.3

2 findings
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Publisher changed: alanhughes → brentvatne (on 2026-05-21) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2026-05-21. This could indicate a legitimate maintainer transition or an account compromise.

v56.0.2

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v56.0.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v56.0.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v55.0.26

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v55.0.25

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v55.0.24

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v55.0.23

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v55.0.22

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v55.0.21

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v55.0.20

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v55.0.19

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v55.0.18

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v55.0.17

2 findings
HIGH New file with network + code execution: src/async-require/__tests__/asyncRequireModule.test.ts source-diff

Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v55.0.10

3 findings
HIGH Publisher changed: brentvatne → alanhughes (on 2026-04-02) provenance

This version was published by a different npm account than previous versions on 2026-04-02. This could indicate a legitimate maintainer transition or an account compromise.

HIGH New file with network + code execution: src/async-require/__tests__/asyncRequireModule.test.ts source-diff

Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v55.0.9

3 findings
HIGH Publisher changed: brentvatne → alanhughes (on 2026-03-27) provenance

This version was published by a different npm account than previous versions on 2026-03-27. This could indicate a legitimate maintainer transition or an account compromise.

HIGH New file with network + code execution: src/async-require/__tests__/asyncRequireModule.test.ts source-diff

Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v55.0.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v54.0.35

2 findings
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Publisher changed: kudochien → alanhughes (on 2026-05-28, known maintainer) provenance

This version was published by a different npm account (alanhughes) than the most recent previously approved version (kudochien) on 2026-05-28, but alanhughes is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v54.0.34

2 findings
HIGH Publisher changed: brentvatne → alanhughes (on 2026-04-27) provenance

This version was published by a different npm account than previous versions on 2026-04-27. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v54.0.33

2 findings
HIGH Publisher changed: brentvatne → kudochien (on 2026-01-31) provenance

This version was published by a different npm account than previous versions on 2026-01-31. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v54.0.32

2 findings
HIGH Publisher changed: brentvatne → alanhughes (on 2026-01-21) provenance

This version was published by a different npm account than previous versions on 2026-01-21. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v54.0.31

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v54.0.30

2 findings
HIGH Publisher changed: brentvatne → alanhughes (on 2025-12-18) provenance

This version was published by a different npm account than previous versions on 2025-12-18. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v54.0.29

2 findings
HIGH Publisher changed: brentvatne → alanhughes (on 2025-12-12) provenance

This version was published by a different npm account than previous versions on 2025-12-12. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v54.0.28

2 findings
HIGH Publisher changed: brentvatne → alanhughes (on 2025-12-11) provenance

This version was published by a different npm account than previous versions on 2025-12-11. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v54.0.27

3 findings
HIGH Publisher changed: gabrieldonadel → kudochien (on 2025-12-05) provenance

This version was published by a different npm account than previous versions on 2025-12-05. This could indicate a legitimate maintainer transition or an account compromise.

HIGH New file with network + code execution: src/async-require/fetchThenEvalJs.ts source-diff

Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v54.0.26

2 findings
HIGH Publisher changed: brentvatne → kudochien (on 2025-12-04) provenance

This version was published by a different npm account than previous versions on 2025-12-04. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v54.0.25

2 findings
HIGH Publisher changed: brentvatne → alanhughes (on 2025-11-18) provenance

This version was published by a different npm account than previous versions on 2025-11-18. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v54.0.24

2 findings
HIGH Publisher changed: brentvatne → alanhughes (on 2025-11-17) provenance

This version was published by a different npm account than previous versions on 2025-11-17. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v54.0.23

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.

v53.0.25

2 findings
HIGH Publisher changed: brentvatne → alanhughes (on 2025-12-11) provenance

This version was published by a different npm account than previous versions on 2025-12-11. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v53.0.24

2 findings
HIGH Publisher changed: brentvatne → kudochien (on 2025-11-18) provenance

This version was published by a different npm account than previous versions on 2025-11-18. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v53.0.9

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.

v52.0.48

2 findings
HIGH Publisher changed: brentvatne → kudochien (on 2025-12-16) provenance

This version was published by a different npm account than previous versions on 2025-12-16. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.