@applitools/image
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| publish-pattern | dormant-publish | AI (publish-pattern): Dormancy explained by Applitools SDK monorepo release cadence; no malicious payload found in this or surrounding versions. | ai | |
| dependencies | unvetted-dep:png-async | AI (dependencies): Image-processing dependency consistent with package purpose; stable across versions. | ai | |
| dependencies | unvetted-dep:bmpimagejs | AI (dependencies): BMP image library consistent with package purpose; stable across versions. | ai | |
| dependencies | unvetted-dep:@applitools/logger | AI (dependencies): Internal Applitools logger dep; same publisher org, stable across versions. | ai |
Versions (showing 13 of 13)
| Version | Deps | Published |
|---|---|---|
| 1.2.11 | 7 / 5 | |
| 1.2.10 | 7 / 5 | |
| 1.2.9 | 7 / 5 | |
| 1.2.8 | 7 / 5 | |
| 1.2.7 | 7 / 5 | |
| 1.2.6 | 5 / 5 | |
| 1.2.5 | 5 / 5 | |
| 1.2.4 | 5 / 5 | |
| 1.2.3 | 5 / 5 | |
| 1.2.2 | 5 / 5 | |
| 1.2.1 | 5 / 5 | |
| 1.2.0 | 5 / 5 | |
| 1.1.21 | 5 / 5 |
v1.2.11
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 (movsho) than the most recent previously approved version (danielputerman) on 2026-05-26, but movsho 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.2.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.4
2 findingsThis version was published by a different npm account than previous versions on 2025-11-10. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.21
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.