@imgly/background-removal
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@types/ndarray | AI (phantom-deps): Type-only convention dep matching ndarray usage. | ai | |
| phantom-deps | phantom-dep:@types/node | AI (phantom-deps): Type-only dep, expected unused-import pattern. | ai | |
| phantom-deps | phantom-dep:@types/lodash | AI (phantom-deps): Type-only dep, expected unused-import pattern. | ai | |
| dependencies | unvetted-dep:ndarray | AI (dependencies): ndarray is a legitimate, well-known npm package for multidimensional arrays; appropriate for an image segmentation library. | ai | |
| phantom-deps | phantom-dep:lodash-es | AI (phantom-deps): Package uses esbuild/webpack bundling; lodash-es is a declared runtime dep that gets bundled into dist files rather than directly imported in source. | ai |
Versions (showing 16 of 16)
| Version | Deps | Published |
|---|---|---|
| 1.7.0 | 3 / 14 | |
| 1.6.0 | 3 / 14 | |
| 1.5.8 | 3 / 14 | |
| 1.5.7 | 4 / 14 | |
| 1.5.6 | 4 / 14 | |
| 1.5.5 | 7 / 11 | |
| 1.5.3 | 7 / 11 | |
| 1.5.2 | 7 / 11 | |
| 1.5.1 | 7 / 11 | |
| 1.5.0 | 7 / 11 | |
| 1.4.5 | 7 / 11 | |
| 1.4.4 | 7 / 11 | |
| 1.4.3 | 6 / 11 | |
| 1.4.2 | 6 / 11 | |
| 1.4.1 | 6 / 11 | |
| 1.4.0 | 6 / 11 |
v1.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.8
2 findingsPackage 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 (danielhauschildt) 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.5.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.