@expo/inline-modules
The Expo inline modules
Supply chain provenance
Status for the latest visible version.
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): brentvatne is a core Expo maintainer with extensive track record; transition from alanhughes within the same org is expected. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): @expo/config-plugins is a core Expo ecosystem package; addition is expected for this monorepo package. | ai |
Versions (showing 18 of 18)
| Version | Deps | Published |
|---|---|---|
| 0.1.3 | 1 / 3 | |
| 0.1.2 | 1 / 3 | |
| 0.1.1 | 1 / 3 | |
| 0.1.0 | 1 / 3 | |
| 0.0.14 | 1 / 3 | |
| 0.0.13 | 1 / 3 | |
| 0.0.12 | 1 / 3 | |
| 0.0.11 | 1 / 3 | |
| 0.0.10 | 1 / 3 | |
| 0.0.9 | 1 / 3 | |
| 0.0.8 | 1 / 3 | |
| 0.0.7 | 1 / 3 | |
| 0.0.6 | 1 / 3 | |
| 0.0.5 | 1 / 3 | |
| 0.0.4 | 1 / 3 | |
| 0.0.3 | 1 / 3 | |
| 0.0.2 | 1 / 3 | |
| 0.0.1 | 0 / 3 |
v0.1.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.1
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (brentvatne) than the most recent previously approved version (alanhughes) on 2026-06-30, 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.
v0.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.13
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (alanhughes) than the most recent previously approved version (brentvatne) on 2026-07-03, 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.