← Home

expo-image-manipulator

npm Repository Homepage

Provides functions that let you manipulation images on the local file system, eg: resize, crop.

38
Versions
MIT
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 — the axios compromise (March 2026) relied on exactly this gap.

Maintainers

idebrentvatneexpoadminexponentbycedrickudochienalanhughestsapetaexpo-botphilplwschurmansjchmiela

Keywords

react-nativeexpoexpo-image-manipulator

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
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 38 of 38)

Version Deps Published
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.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

v56.0.18

2 findings
INFO No provenance attestation provenance

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

INFO Publisher changed: brentvatne → alanhughes (on 2026-06-10, known maintainer) provenance

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

v56.0.17

2 findings
INFO No provenance attestation provenance

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

INFO Publisher changed: alanhughes → brentvatne (on 2026-06-05, known maintainer) provenance

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

2 findings
HIGH Bundled binary files (6) npm-metadata

Package contains compiled binaries that could be backdoors: • prebuilds/spm-deps/SDWebImage/debug/SDWebImage.xcframework/ios-arm64/SDWebImage.framework/SDWebImage • prebuilds/spm-deps/SDWebImage/release/SDWebImage.xcframework/ios-arm64/dSYMs/SDWebImage.framework.dSYM/Contents/Resources/DWARF/SDWebImage • prebuilds/spm-deps/SDWebImage/release/SDWebImage.xcframework/ios-arm64/SDWebImage.framework/SDWebImage • prebuilds/spm-deps/SDWebImageWebPCoder/debug/SDWebImageWebPCoder.xcframework/ios-arm64/SDWebImageWebPCoder.framework/SDWebImageWebPCoder • prebuilds/spm-deps/SDWebImageWebPCoder/release/SDWebImageWebPCoder.xcframework/ios-arm64/dSYMs/SDWebImageWebPCoder.framework.dSYM/Contents/Resources/DWARF/SDWebImageWebPCoder • prebuilds/spm-deps/SDWebImageWebPCoder/release/SDWebImageWebPCoder.xcframework/ios-arm64/SDWebImageWebPCoder.framework/SDWebImageWebPCoder

INFO No provenance attestation provenance

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

v56.0.15

2 findings
HIGH Bundled binary files (6) npm-metadata

Package contains compiled binaries that could be backdoors: • prebuilds/spm-deps/SDWebImage/debug/SDWebImage.xcframework/ios-arm64/SDWebImage.framework/SDWebImage • prebuilds/spm-deps/SDWebImage/release/SDWebImage.xcframework/ios-arm64/dSYMs/SDWebImage.framework.dSYM/Contents/Resources/DWARF/SDWebImage • prebuilds/spm-deps/SDWebImage/release/SDWebImage.xcframework/ios-arm64/SDWebImage.framework/SDWebImage • prebuilds/spm-deps/SDWebImageWebPCoder/debug/SDWebImageWebPCoder.xcframework/ios-arm64/SDWebImageWebPCoder.framework/SDWebImageWebPCoder • prebuilds/spm-deps/SDWebImageWebPCoder/release/SDWebImageWebPCoder.xcframework/ios-arm64/dSYMs/SDWebImageWebPCoder.framework.dSYM/Contents/Resources/DWARF/SDWebImageWebPCoder • prebuilds/spm-deps/SDWebImageWebPCoder/release/SDWebImageWebPCoder.xcframework/ios-arm64/SDWebImageWebPCoder.framework/SDWebImageWebPCoder

INFO No provenance attestation provenance

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

v56.0.14

2 findings
HIGH Bundled binary files (6) npm-metadata

Package contains compiled binaries that could be backdoors: • prebuilds/spm-deps/SDWebImage/debug/SDWebImage.xcframework/ios-arm64/SDWebImage.framework/SDWebImage • prebuilds/spm-deps/SDWebImage/release/SDWebImage.xcframework/ios-arm64/dSYMs/SDWebImage.framework.dSYM/Contents/Resources/DWARF/SDWebImage • prebuilds/spm-deps/SDWebImage/release/SDWebImage.xcframework/ios-arm64/SDWebImage.framework/SDWebImage • prebuilds/spm-deps/SDWebImageWebPCoder/debug/SDWebImageWebPCoder.xcframework/ios-arm64/SDWebImageWebPCoder.framework/SDWebImageWebPCoder • prebuilds/spm-deps/SDWebImageWebPCoder/release/SDWebImageWebPCoder.xcframework/ios-arm64/dSYMs/SDWebImageWebPCoder.framework.dSYM/Contents/Resources/DWARF/SDWebImageWebPCoder • prebuilds/spm-deps/SDWebImageWebPCoder/release/SDWebImageWebPCoder.xcframework/ios-arm64/SDWebImageWebPCoder.framework/SDWebImageWebPCoder

INFO No provenance attestation provenance

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

v56.0.13

3 findings
HIGH Bundled binary files (6) npm-metadata

Package contains compiled binaries that could be backdoors: • prebuilds/spm-deps/SDWebImage/debug/SDWebImage.xcframework/ios-arm64/SDWebImage.framework/SDWebImage • prebuilds/spm-deps/SDWebImage/release/SDWebImage.xcframework/ios-arm64/dSYMs/SDWebImage.framework.dSYM/Contents/Resources/DWARF/SDWebImage • prebuilds/spm-deps/SDWebImage/release/SDWebImage.xcframework/ios-arm64/SDWebImage.framework/SDWebImage • prebuilds/spm-deps/SDWebImageWebPCoder/debug/SDWebImageWebPCoder.xcframework/ios-arm64/SDWebImageWebPCoder.framework/SDWebImageWebPCoder • prebuilds/spm-deps/SDWebImageWebPCoder/release/SDWebImageWebPCoder.xcframework/ios-arm64/dSYMs/SDWebImageWebPCoder.framework.dSYM/Contents/Resources/DWARF/SDWebImageWebPCoder • prebuilds/spm-deps/SDWebImageWebPCoder/release/SDWebImageWebPCoder.xcframework/ios-arm64/SDWebImageWebPCoder.framework/SDWebImageWebPCoder

HIGH Publisher changed: alanhughes → brentvatne (on 2026-05-21) provenance

This version was published by a different npm account than previous versions on 2026-05-21. This could indicate a legitimate maintainer transition or an account compromise.

INFO No provenance attestation provenance

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

v56.0.12

2 findings
HIGH Bundled binary files (6) npm-metadata

Package contains compiled binaries that could be backdoors: • prebuilds/spm-deps/SDWebImage/debug/SDWebImage.xcframework/ios-arm64/SDWebImage.framework/SDWebImage • prebuilds/spm-deps/SDWebImage/release/SDWebImage.xcframework/ios-arm64/dSYMs/SDWebImage.framework.dSYM/Contents/Resources/DWARF/SDWebImage • prebuilds/spm-deps/SDWebImage/release/SDWebImage.xcframework/ios-arm64/SDWebImage.framework/SDWebImage • prebuilds/spm-deps/SDWebImageWebPCoder/debug/SDWebImageWebPCoder.xcframework/ios-arm64/SDWebImageWebPCoder.framework/SDWebImageWebPCoder • prebuilds/spm-deps/SDWebImageWebPCoder/release/SDWebImageWebPCoder.xcframework/ios-arm64/dSYMs/SDWebImageWebPCoder.framework.dSYM/Contents/Resources/DWARF/SDWebImageWebPCoder • prebuilds/spm-deps/SDWebImageWebPCoder/release/SDWebImageWebPCoder.xcframework/ios-arm64/SDWebImageWebPCoder.framework/SDWebImageWebPCoder

INFO No provenance attestation provenance

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

v56.0.11

1 finding
INFO No provenance attestation provenance

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

v56.0.10

1 finding
INFO No provenance attestation provenance

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

v56.0.9

1 finding
INFO No provenance attestation provenance

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

v56.0.8

2 findings
HIGH Publisher changed: alanhughes → brentvatne (on 2026-05-14) provenance

This version was published by a different npm account than previous versions on 2026-05-14. This could indicate a legitimate maintainer transition or an account compromise.

INFO No provenance attestation provenance

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

v56.0.7

1 finding
INFO No provenance attestation provenance

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

v56.0.6

1 finding
INFO No provenance attestation provenance

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

v56.0.5

1 finding
INFO No provenance attestation provenance

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

v56.0.4

1 finding
INFO No provenance attestation provenance

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

v56.0.3

1 finding
INFO No provenance attestation provenance

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

v56.0.2

1 finding
INFO No provenance attestation provenance

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

v56.0.1

1 finding
INFO No provenance attestation provenance

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

v56.0.0

1 finding
INFO No provenance attestation provenance

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

v55.0.17

2 findings
HIGH Bundled binary files (6) npm-metadata

Package contains compiled binaries that could be backdoors: • prebuilds/spm-deps/SDWebImage/debug/SDWebImage.xcframework/ios-arm64/SDWebImage.framework/SDWebImage • prebuilds/spm-deps/SDWebImage/release/SDWebImage.xcframework/ios-arm64/dSYMs/SDWebImage.framework.dSYM/Contents/Resources/DWARF/SDWebImage • prebuilds/spm-deps/SDWebImage/release/SDWebImage.xcframework/ios-arm64/SDWebImage.framework/SDWebImage • prebuilds/spm-deps/SDWebImageWebPCoder/debug/SDWebImageWebPCoder.xcframework/ios-arm64/SDWebImageWebPCoder.framework/SDWebImageWebPCoder • prebuilds/spm-deps/SDWebImageWebPCoder/release/SDWebImageWebPCoder.xcframework/ios-arm64/dSYMs/SDWebImageWebPCoder.framework.dSYM/Contents/Resources/DWARF/SDWebImageWebPCoder • prebuilds/spm-deps/SDWebImageWebPCoder/release/SDWebImageWebPCoder.xcframework/ios-arm64/SDWebImageWebPCoder.framework/SDWebImageWebPCoder

INFO No provenance attestation provenance

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

v55.0.16

1 finding
INFO No provenance attestation provenance

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

v55.0.14

1 finding
INFO No provenance attestation provenance

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

v55.0.13

1 finding
INFO No provenance attestation provenance

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

v55.0.12

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v55.0.11

2 findings
HIGH Publisher changed: kudochien → alanhughes (on 2026-03-17) provenance

This version was published by a different npm account than previous versions on 2026-03-17. This could indicate a legitimate maintainer transition or an account compromise.

INFO No provenance attestation provenance

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

v55.0.10

2 findings
HIGH Publisher changed: kudochien → alanhughes (on 2026-03-11) provenance

This version was published by a different npm account than previous versions on 2026-03-11. This could indicate a legitimate maintainer transition or an account compromise.

INFO No provenance attestation provenance

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

v55.0.9

2 findings
HIGH Publisher changed: kudochien → brentvatne (on 2026-02-25) provenance

This version was published by a different npm account than previous versions on 2026-02-25. This could indicate a legitimate maintainer transition or an account compromise.

INFO No provenance attestation provenance

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

v55.0.8

2 findings
HIGH Publisher changed: kudochien → alanhughes (on 2026-02-20) provenance

This version was published by a different npm account than previous versions on 2026-02-20. This could indicate a legitimate maintainer transition or an account compromise.

INFO No provenance attestation provenance

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

v55.0.7

2 findings
HIGH Publisher changed: kudochien → alanhughes (on 2026-02-20) provenance

This version was published by a different npm account than previous versions on 2026-02-20. This could indicate a legitimate maintainer transition or an account compromise.

INFO No provenance attestation provenance

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

v55.0.6

2 findings
HIGH Publisher changed: kudochien → alanhughes (on 2026-02-16) provenance

This version was published by a different npm account than previous versions on 2026-02-16. This could indicate a legitimate maintainer transition or an account compromise.

INFO No provenance attestation provenance

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

v55.0.5

2 findings
HIGH Publisher changed: kudochien → brentvatne (on 2026-02-08) provenance

This version was published by a different npm account than previous versions on 2026-02-08. This could indicate a legitimate maintainer transition or an account compromise.

INFO No provenance attestation provenance

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

v55.0.4

2 findings
HIGH Publisher changed: kudochien → brentvatne (on 2026-02-03) provenance

This version was published by a different npm account than previous versions on 2026-02-03. This could indicate a legitimate maintainer transition or an account compromise.

INFO No provenance attestation provenance

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

v55.0.3

2 findings
HIGH Publisher changed: kudochien → brentvatne (on 2026-01-27) provenance

This version was published by a different npm account than previous versions on 2026-01-27. This could indicate a legitimate maintainer transition or an account compromise.

INFO No provenance attestation provenance

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

v55.0.2

2 findings
HIGH Publisher changed: kudochien → brentvatne (on 2026-01-26) provenance

This version was published by a different npm account than previous versions on 2026-01-26. This could indicate a legitimate maintainer transition or an account compromise.

INFO No provenance attestation provenance

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

v55.0.1

2 findings
HIGH Publisher changed: kudochien → alanhughes (on 2026-01-22) provenance

This version was published by a different npm account than previous versions on 2026-01-22. This could indicate a legitimate maintainer transition or an account compromise.

INFO No provenance attestation provenance

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

v55.0.0

2 findings
HIGH Publisher changed: kudochien → brentvatne (on 2026-01-21) provenance

This version was published by a different npm account than previous versions on 2026-01-21. This could indicate a legitimate maintainer transition or an account compromise.

INFO No provenance attestation provenance

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

v14.0.8

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.