← Home

expo-constants-interface

An interface for expo-constants.

7
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-nativeexpoconstants

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): Publisher change from sjchmiela to brentvatne reflects normal Expo team rotation; both are recognized Expo core contributors under the expo/expo monorepo. ai
maintainer-change maintainer-added AI (maintainer-change): New maintainers janicduplessis and wkozyra are known Expo team members; addition is consistent with legitimate org-level team management. ai
maintainer-change maintainer-removed AI (maintainer-change): Removal of jakubste is consistent with normal Expo team rotation, not a hostile takeover signal. ai
provenance no-provenance AI (provenance): Package was published in 2019, predating Sigstore/npm provenance attestation; absence is expected for this era. ai

Versions (showing 7 of 7)

Version Deps Published
3.0.0 0 / 1
2.0.0 1 / 0
1.1.0 1 / 0
1.0.2 1 / 0
1.0.1 1 / 0
1.0.0 1 / 0
0.0.1 0 / 0

v3.0.0

2 findings
HIGH Publisher changed: sjchmiela → brentvatne (on 2019-02-27) provenance

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

v2.0.0

2 findings
INFO No provenance attestation provenance

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

INFO Publisher changed: tsapeta → sjchmiela (on 2019-01-04) provenance

[Accepted risk] 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.