← Home

expo-core

npm Repository Homepage

The core Expo universal module between application code and the underlying platform

10
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

barthecbrentvatneccheeverdsokalesamelsonevanbaconexpoadminexponentfsonidejanicduplessisjesserudernikki93quinlanjsjchmielaterriblebentsapetawkozyra

Keywords

react-nativeexpo

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): Both tsapeta and sjchmiela are known Expo/650 Industries team members; publisher changes within this org are routine internal transitions, not compromise signals. ai
maintainer-change maintainer-added AI (maintainer-change): New maintainers barthec and quinlanj are Expo team members; additions within the official Expo org are expected as the team grows. ai

Versions (showing 10 of 10)

Version Deps Published
3.0.1 0 / 1
3.0.0 0 / 1
2.0.2 0 / 1
2.0.1 0 / 1
2.0.0 0 / 1
1.2.0 0 / 0
1.1.0 0 / 0
1.0.1 0 / 0
1.0.0 0 / 0
0.0.1 0 / 0

v3.0.1

1 finding
LOW No provenance attestation provenance

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

v3.0.0

1 finding
LOW No provenance attestation provenance

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

v2.0.2

1 finding
LOW No provenance attestation provenance

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

v2.0.1

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: sjchmiela → brentvatne (on 2019-02-14) provenance

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

v2.0.0

2 findings
HIGH Publisher changed: tsapeta → sjchmiela (on 2019-01-04) provenance

This version was published by a different npm account than previous versions on 2019-01-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.