@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, 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 | 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 29 of 29)
| Version | Deps | Published |
|---|---|---|
| 1.78.0 | 1 / 9 | |
| 1.77.1 | 1 / 9 | |
| 1.77.0 | 1 / 9 | |
| 1.76.1 | 1 / 9 | |
| 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 | |
| 1.1.0 | 1 / 10 | |
| 1.0.4 | 1 / 9 | |
| 1.0.3 | 1 / 9 | |
| 1.0.2 | 1 / 9 | |
| 1.0.1 | 1 / 8 | |
| 1.0.0 | 1 / 8 |
v1.78.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.77.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.77.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.3
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 (mirko314-imgly) than the most recent previously approved version (maerch) on 2025-01-24, but mirko314-imgly 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.
v1.0.2
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 (maerch) than the most recent previously approved version (mirko314-imgly) on 2024-12-20, but maerch 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.
v1.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.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.