@imgly/plugin-background-removal-web
Background Removal plugin for the CE.SDK editor
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 | no-provenance | AI (provenance): Established commercial package from IMG.LY GmbH; lack of Sigstore provenance is consistent across their entire SDK plugin ecosystem. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): IMG.LY coordinates releases across their SDK ecosystem; version bumps track @cesdk/cesdk-js peer dep versions. Dormancy gaps are consistent with their release cadence, not account takeover. | ai | |
| dependencies | unvetted-dep:@imgly/background-removal | AI (dependencies): First-party IMG.LY dependency; same organization publishes both packages. Not a third-party risk. | ai | |
| dependencies | unvetted-peer-dep:@cesdk/cesdk-js | AI (dependencies): First-party IMG.LY CE.SDK peer dependency; consumers of this plugin already use it as the host editor. | ai |
Versions (showing 19 of 19)
| Version | Deps | Published |
|---|---|---|
| 1.76.0 | 1 / 9 | |
| 1.75.1 | 1 / 9 | |
| 1.75.0 | 1 / 9 | |
| 1.74.2 | 1 / 9 | |
| 1.74.1 | 1 / 9 | |
| 1.74.0 | 1 / 9 | |
| 1.73.1 | 1 / 9 | |
| 1.73.0 | 1 / 9 | |
| 1.72.3 | 1 / 9 | |
| 1.72.2 | 1 / 9 | |
| 1.72.1 | 1 / 9 | |
| 1.72.0 | 1 / 9 | |
| 1.71.0 | 1 / 9 | |
| 1.70.1 | 1 / 9 | |
| 1.70.0 | 1 / 9 | |
| 1.69.0 | 1 / 9 | |
| 1.68.0 | 1 / 9 | |
| 1.2.1 | 1 / 10 | |
| 1.2.0 | 1 / 10 |
v1.76.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.75.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.75.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.74.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.74.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.74.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.73.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.73.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.72.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.72.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.72.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.72.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.71.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.70.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.70.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.69.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.68.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.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.
v1.2.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.