← Home

expo-build-properties

npm Repository Homepage
51
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-nativeexpobuildbuild-properties

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): alanhughes is an established Expo org maintainer with strong track record; transition from brentvatne is a legitimate org handoff. ai
publish-pattern new-deps-added AI (publish-pattern): @expo/schema-utils is an Expo-org package replacing ajv; benign internal refactor for this package. ai

Versions (showing 51 of 51)

Version Deps Published
57.0.7 3 / 4
57.0.6 3 / 4
57.0.5 3 / 4
57.0.4 3 / 4
57.0.3 3 / 4
57.0.2 3 / 4
57.0.1 3 / 4
57.0.0 3 / 4
56.0.24 3 / 4
56.0.23 3 / 4
56.0.22 3 / 4
56.0.21 3 / 4
56.0.20 3 / 4
56.0.19 3 / 4
56.0.18 3 / 4
56.0.17 3 / 4
56.0.16 3 / 4
56.0.15 3 / 4
56.0.14 3 / 4
56.0.13 3 / 4
56.0.12 3 / 4
56.0.11 3 / 4
56.0.10 3 / 4
56.0.9 3 / 4
56.0.8 3 / 4
56.0.7 3 / 4
56.0.6 3 / 4
56.0.5 3 / 4
56.0.4 3 / 4
56.0.3 3 / 4
56.0.2 3 / 4
56.0.1 3 / 4
56.0.0 3 / 3
55.0.16 3 / 1
55.0.15 3 / 1
55.0.14 3 / 1
55.0.13 3 / 1
55.0.12 3 / 1
55.0.11 3 / 1
55.0.10 3 / 1
55.0.9 3 / 1
55.0.8 3 / 1
55.0.7 3 / 1
55.0.6 3 / 1
55.0.5 3 / 1
55.0.4 3 / 1
55.0.3 2 / 1
55.0.2 2 / 1
55.0.1 2 / 1
55.0.0 2 / 1
1.0.10 2 / 1

v57.0.7

1 finding
LOW No provenance attestation provenance

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

v57.0.6

1 finding
LOW No provenance attestation provenance

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

v57.0.5

1 finding
LOW No provenance attestation provenance

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

v57.0.4

1 finding
LOW No provenance attestation provenance

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

v57.0.3

1 finding
LOW No provenance attestation provenance

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

v57.0.2

1 finding
LOW No provenance attestation provenance

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

v57.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: alanhughes → brentvatne (on 2026-06-27, known maintainer) provenance

This version was published by a different npm account (brentvatne) than the most recent previously approved version (alanhughes) on 2026-06-27, but brentvatne 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.24

1 finding
LOW No provenance attestation provenance

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

v56.0.23

1 finding
LOW No provenance attestation provenance

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

v56.0.22

1 finding
LOW No provenance attestation provenance

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

v56.0.21

1 finding
LOW No provenance attestation provenance

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

v56.0.20

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-07-01, known maintainer) provenance

This version was published by a different npm account (alanhughes) than the most recent previously approved version (brentvatne) on 2026-07-01, 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.

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.