@expo/config-plugins
A library for Expo config plugins
Supply chain provenance
Status for the latest visible version.
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | missing-githead | AI (provenance): Canary releases from the Expo monorepo are published via a different pipeline that does not inject gitHead; this is a consistent pattern for @expo/* canary versions and not a malicious signal. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): Expo is a large open-source org; maintainer roster changes are routine. New maintainers (douglowder, betoatexpo, philpl) are consistent with known Expo team members. | ai | |
| dependencies | unvetted-dep:@expo/fingerprint | AI (dependencies): @expo/fingerprint is an Expo-maintained package in the same monorepo/org; not a third-party unknown. Stable false positive for this package. | ai | |
| publish-pattern | suspicious-version-number | AI (publish-pattern): Expo uses a documented canary versioning pattern (X.Y.Z-canary-YYYYMMDD-githash) for pre-release builds; this is not a malicious version string pattern for this package. | ai | |
| phantom-deps | phantom-dep:@react-native/normalize-color | AI (phantom-deps): @react-native/normalize-color is an official Meta/React Native package declared for platform-specific resolution; not directly imported in JS is expected behavior for this type of dep. | ai | |
| dependencies | unvetted-dep:@expo/config-types | AI (dependencies): First-party Expo package from the same monorepo; part of the official Expo ecosystem. | ai | |
| dependencies | unvetted-dep:@expo/sdk-runtime-versions | AI (dependencies): First-party Expo package from the same monorepo; part of the official Expo ecosystem. | ai | |
| dependencies | unvetted-dep:xcode | AI (dependencies): xcode is a well-known npm package for parsing Xcode project files, a standard dependency for React Native/Expo tooling. | ai | |
| dependencies | unvetted-dep:getenv | AI (dependencies): getenv is a small, established utility for reading environment variables; standard dependency for build tooling. | ai | |
| dependencies | unvetted-dep:xml2js | AI (dependencies): xml2js is a widely-used XML parsing library; pinned to 0.6.0 which is a stable release. | ai | |
| dependencies | unvetted-dep:slugify | AI (dependencies): slugify is a well-established string slugification utility with no known security issues. | ai | |
| dependencies | unvetted-dep:@expo/json-file | AI (dependencies): First-party Expo package from the same monorepo; part of the official Expo ecosystem. | ai | |
| provenance | publisher-changed | AI (provenance): brentvatne is a core Expo team member with an exceptional track record (3555 approved versions). Publisher rotation within the Expo org is expected and not a takeover signal. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Maintainer changes within the Expo organization are routine team transitions, not indicative of a package takeover. | ai | |
| provenance | no-provenance | AI (provenance): Expo monorepo packages historically lack Sigstore provenance; this is consistent with the publisher's other approved packages and not a risk indicator for this ecosystem. | ai |
Versions (showing 79 of 179)
| Version | Deps | Published |
|---|---|---|
| 6.0.2 | 15 / 3 | |
| 6.0.1 | 15 / 3 | |
| 6.0.0 | 15 / 3 | |
| 5.0.4 | 15 / 3 | |
| 5.0.3 | 15 / 3 | |
| 5.0.2 | 15 / 3 | |
| 5.0.1 | 15 / 3 | |
| 5.0.0 | 15 / 3 | |
| 4.1.5 | 15 / 3 | |
| 4.1.4 | 15 / 3 | |
| 4.1.3 | 15 / 3 | |
| 4.1.2 | 15 / 3 | |
| 4.1.1 | 15 / 3 | |
| 4.1.0 | 16 / 4 | |
| 4.0.18 | 16 / 4 | |
| 4.0.17 | 16 / 4 | |
| 4.0.16 | 16 / 4 | |
| 4.0.15 | 16 / 4 | |
| 4.0.14 | 16 / 4 | |
| 4.0.13 | 16 / 4 | |
| 4.0.12 | 16 / 4 | |
| 4.0.11 | 16 / 4 | |
| 4.0.10 | 15 / 4 | |
| 4.0.9 | 15 / 4 | |
| 4.0.8 | 15 / 4 | |
| 4.0.7 | 15 / 4 | |
| 4.0.6 | 15 / 4 | |
| 4.0.4 | 15 / 4 | |
| 4.0.3 | 15 / 4 | |
| 4.0.2 | 15 / 4 | |
| 4.0.0 | 15 / 4 | |
| 3.1.0 | 14 / 4 | |
| 3.0.8 | 13 / 4 | |
| 3.0.7 | 13 / 4 | |
| 3.0.6 | 13 / 4 | |
| 3.0.5 | 13 / 6 | |
| 3.0.4 | 13 / 6 | |
| 3.0.3 | 12 / 6 | |
| 3.0.2 | 12 / 6 | |
| 3.0.1 | 12 / 6 | |
| 3.0.0 | 12 / 6 | |
| 2.0.4 | 12 / 6 | |
| 2.0.3 | 12 / 6 | |
| 2.0.2 | 11 / 5 | |
| 2.0.1 | 11 / 5 | |
| 2.0.0 | 11 / 5 | |
| 1.0.33 | 13 / 5 | |
| 1.0.32 | 14 / 5 | |
| 1.0.31 | 14 / 5 | |
| 1.0.30 | 14 / 5 | |
| 1.0.29 | 14 / 5 | |
| 1.0.28 | 14 / 5 | |
| 1.0.27 | 14 / 5 | |
| 1.0.26 | 14 / 5 | |
| 1.0.25 | 14 / 5 | |
| 1.0.24 | 14 / 5 | |
| 1.0.23 | 14 / 5 | |
| 1.0.22 | 14 / 5 | |
| 1.0.21 | 14 / 5 | |
| 1.0.20 | 14 / 5 | |
| 1.0.19 | 14 / 5 | |
| 1.0.18 | 14 / 5 | |
| 1.0.17 | 13 / 5 | |
| 1.0.16 | 13 / 5 | |
| 1.0.15 | 13 / 5 | |
| 1.0.14 | 13 / 5 | |
| 1.0.13 | 12 / 4 | |
| 1.0.12 | 13 / 4 | |
| 1.0.11 | 13 / 4 | |
| 1.0.10 | 12 / 4 | |
| 1.0.9 | 12 / 4 | |
| 1.0.8 | 12 / 4 | |
| 1.0.7 | 11 / 4 | |
| 1.0.6 | 11 / 4 | |
| 1.0.5 | 11 / 4 | |
| 1.0.4 | 11 / 4 | |
| 1.0.3 | 11 / 4 | |
| 1.0.2 | 11 / 4 | |
| 1.0.1 | 11 / 4 |
v6.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.18
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.17
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.16
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.15
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.33
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.32
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.31
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.30
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.29
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.28
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.27
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.26
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.25
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.24
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.23
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.22
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.21
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.20
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.19
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.18
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.17
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.16
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.15
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.