← Home

expo-secure-store

npm Repository Homepage
25
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, so a manually published version cannot be tied back to a reviewed commit.

Maintainers

idebrentvatneexpoadminexponentbycedrickudochienalanhughestsapetaexpo-botphilplwschurman

Keywords

react-nativeexpoexpo-secure-storesecurestore

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 publisher with extensive track record; team rotation is normal. ai
maintainer-change maintainer-removed AI (maintainer-change): Normal Expo team rotation; kadikraman removal is consistent with org changes. ai
publish-pattern dormant-publish AI (publish-pattern): False positive: Expo SDK version jump (v15→v55) not real dormancy. ai

Versions (showing 25 of 25)

Version Deps Published
57.0.1 0 / 3
57.0.0 0 / 3
56.0.4 0 / 3
56.0.3 0 / 3
56.0.2 0 / 3
56.0.1 0 / 3
56.0.0 0 / 2
55.0.16 0 / 1
55.0.15 0 / 1
55.0.14 0 / 1
55.0.13 0 / 1
55.0.12 0 / 1
55.0.11 0 / 1
55.0.10 0 / 1
55.0.9 0 / 1
55.0.8 0 / 1
55.0.7 0 / 1
55.0.6 0 / 1
55.0.5 0 / 1
55.0.4 0 / 1
55.0.3 0 / 1
55.0.2 0 / 1
55.0.1 0 / 1
55.0.0 0 / 1
15.0.8 0 / 1

v57.0.1

1 finding
LOW No provenance attestation provenance

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

v55.0.16

1 finding
LOW No provenance attestation provenance

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