expo-image-manipulator
Provides functions that let you manipulation images on the local file system, eg: resize, crop.
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): alanhughes is a known Expo org publisher; rotation among Expo team members is expected. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Normal Expo team roster changes; kadikraman departure is a known org transition. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Expo SDK packages publish in waves per SDK release; gaps between major versions are normal. | ai | |
| npm-metadata | bundled-binaries | AI (npm-metadata): Prebuilt iOS xcframework binaries (SDWebImage) are expected for this Expo native module. | ai | |
| provenance | no-provenance | AI (provenance): Expo SDK packages are published from the official expo/expo monorepo without Sigstore provenance; this is consistent across the package family and not a risk indicator. | ai | |
| phantom-deps | phantom-dep:expo-image-loader | AI (phantom-deps): expo-image-loader is a sibling Expo SDK package referenced in native config/build files rather than JS imports; this is expected for native module packages in the Expo ecosystem. | ai |
Versions (showing 50 of 50)
| Version | Deps | Published |
|---|---|---|
| 57.0.5 | 1 / 2 | |
| 57.0.4 | 1 / 2 | |
| 57.0.3 | 1 / 2 | |
| 57.0.2 | 1 / 2 | |
| 57.0.1 | 1 / 2 | |
| 57.0.0 | 1 / 2 | |
| 56.0.22 | 1 / 2 | |
| 56.0.21 | 1 / 2 | |
| 56.0.20 | 1 / 2 | |
| 56.0.19 | 1 / 2 | |
| 56.0.18 | 1 / 2 | |
| 56.0.17 | 1 / 2 | |
| 56.0.16 | 1 / 2 | |
| 56.0.15 | 1 / 2 | |
| 56.0.14 | 1 / 2 | |
| 56.0.13 | 1 / 2 | |
| 56.0.12 | 1 / 2 | |
| 56.0.11 | 1 / 2 | |
| 56.0.10 | 1 / 2 | |
| 56.0.9 | 1 / 2 | |
| 56.0.8 | 1 / 2 | |
| 56.0.7 | 1 / 2 | |
| 56.0.6 | 1 / 2 | |
| 56.0.5 | 1 / 2 | |
| 56.0.4 | 1 / 2 | |
| 56.0.3 | 1 / 2 | |
| 56.0.2 | 1 / 2 | |
| 56.0.1 | 1 / 2 | |
| 56.0.0 | 1 / 1 | |
| 55.0.19 | 1 / 1 | |
| 55.0.18 | 1 / 1 | |
| 55.0.17 | 1 / 1 | |
| 55.0.16 | 1 / 1 | |
| 55.0.15 | 1 / 1 | |
| 55.0.14 | 1 / 1 | |
| 55.0.13 | 1 / 1 | |
| 55.0.12 | 1 / 1 | |
| 55.0.11 | 1 / 1 | |
| 55.0.10 | 1 / 1 | |
| 55.0.9 | 1 / 1 | |
| 55.0.8 | 1 / 1 | |
| 55.0.7 | 1 / 1 | |
| 55.0.6 | 1 / 1 | |
| 55.0.5 | 1 / 1 | |
| 55.0.4 | 1 / 1 | |
| 55.0.3 | 1 / 1 | |
| 55.0.2 | 1 / 1 | |
| 55.0.1 | 1 / 1 | |
| 55.0.0 | 1 / 1 | |
| 14.0.8 | 1 / 1 |
v57.0.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v57.0.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v57.0.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v57.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v57.0.1
2 findings[Accepted risk] Package 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-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.22
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v56.0.21
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v56.0.20
2 findings[Accepted risk] Package 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-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.19
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.