← Home

@imgly/editor-react-native

CreativeEditor SDK for React Native - enable photo, video and design editing for your users on iOS and Android.

50
Versions
SEE LICENSE IN LICENSE.md
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

danielhauschildtschiewesascha_svendvdleon_dudmirko314-imglymaerchravenszewczyk-imglyelia-darwishmaltebaumannjonashartwighiyeon

Keywords

react-nativeiosandroidcesdkeditorimgly

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): New publisher has strong 179-package track record; no behavioral changes in diff. ai
maintainer-change maintainer-added AI (maintainer-change): Consistent with legitimate maintainer addition, no malicious diff. ai

Versions (showing 50 of 50)

Version Deps Published
1.78.0 0 / 0
1.77.0 0 / 0
1.76.1 0 / 0
1.76.0 0 / 0
1.75.1 0 / 0
1.74.0 0 / 0
1.73.1 0 / 0
1.73.0 0 / 0
1.72.3 0 / 0
1.72.0 0 / 0
1.71.0 0 / 0
1.70.0 0 / 0
1.69.0 0 / 0
1.68.0 0 / 0
1.67.0 0 / 0
1.66.0 0 / 0
1.65.0 0 / 0
1.64.0 0 / 0
1.63.0 0 / 0
1.62.0 0 / 0
1.61.0 0 / 0
1.60.0 0 / 0
1.59.0 0 / 0
1.58.0 0 / 0
1.57.1 0 / 0
1.57.0 0 / 0
1.56.0 0 / 0
1.55.2 0 / 0
1.55.1 0 / 0
1.55.0 0 / 0
1.54.1 0 / 0
1.54.0 0 / 0
1.53.0 0 / 0
1.52.0 0 / 0
1.51.0 0 / 0
1.50.2 0 / 0
1.50.1 0 / 0
1.50.0 0 / 0
1.49.0 0 / 0
1.48.0 0 / 0
1.47.0 0 / 0
1.46.0 0 / 0
1.45.0 0 / 0
1.44.0 0 / 0
1.43.0 0 / 0
1.42.0 0 / 0
1.41.1 0 / 0
1.41.0 0 / 0
1.40.1 0 / 0
1.40.0 0 / 0

v1.78.0

1 finding
LOW No provenance attestation provenance

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

v1.77.0

1 finding
LOW No provenance attestation provenance

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

v1.76.1

1 finding
LOW No provenance attestation provenance

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

v1.49.0

2 findings
HIGH Publisher changed: leon_dud → maltebaumann (on 2025-04-24) provenance

This version was published by a different npm account than previous versions on 2025-04-24. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

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

v1.48.0

2 findings
HIGH Publisher changed: leon_dud → maltebaumann (on 2025-04-17) provenance

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

LOW No provenance attestation provenance

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

v1.47.0

2 findings
HIGH Publisher changed: leon_dud → maltebaumann (on 2025-03-27) provenance

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

LOW No provenance attestation provenance

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

v1.46.0

2 findings
HIGH Publisher changed: leon_dud → maltebaumann (on 2025-03-27) provenance

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

LOW No provenance attestation provenance

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

v1.45.0

2 findings
HIGH Publisher changed: leon_dud → maltebaumann (on 2025-02-25) provenance

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

LOW No provenance attestation provenance

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

v1.44.0

2 findings
HIGH Publisher changed: leon_dud → maltebaumann (on 2025-02-25) provenance

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

LOW No provenance attestation provenance

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

v1.43.0

2 findings
HIGH Publisher changed: leon_dud → maltebaumann (on 2025-02-05) provenance

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

LOW No provenance attestation provenance

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

v1.42.0

2 findings
HIGH Publisher changed: leon_dud → maltebaumann (on 2025-01-27) provenance

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

LOW No provenance attestation provenance

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

v1.41.1

2 findings
HIGH Publisher changed: leon_dud → maltebaumann (on 2025-01-09) provenance

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

LOW No provenance attestation provenance

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

v1.41.0

2 findings
HIGH Publisher changed: leon_dud → maltebaumann (on 2025-01-09) provenance

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

LOW No provenance attestation provenance

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

v1.40.1

2 findings
HIGH Publisher changed: leon_dud → maltebaumann (on 2025-01-09) provenance

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

LOW No provenance attestation provenance

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

v1.40.0

1 finding
LOW No provenance attestation provenance

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