@applitools/eyes-cypress
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 |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): movsho is an established Applitools publisher with 396 approved packages; transition appears legitimate. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Applitools SDK with 325 published versions; inactivity gap is plausible for a mature SDK, no malicious indicators present. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Long-standing package; missing description is metadata gap, not malware signal. | ai | |
| provenance | no-provenance | AI (provenance): Provenance is uncommon in npm ecosystem; not a disqualifier for established packages. | ai | |
| dependencies | unvetted-dep:@applitools/core-universal | AI (dependencies): First-party Applitools dependency; stable pattern across all versions of this SDK. | ai | |
| dependencies | unvetted-dep:@applitools/core | AI (dependencies): First-party Applitools dependency; stable pattern across all versions of this SDK. | ai | |
| dependencies | unvetted-dep:@applitools/functional-commons | AI (dependencies): First-party Applitools dependency; stable pattern across all versions of this SDK. | ai | |
| dependencies | unvetted-dep:@applitools/eyes | AI (dependencies): First-party Applitools dependency; stable pattern across all versions of this SDK. | ai | |
| dependencies | unvetted-dep:@applitools/utils | AI (dependencies): First-party Applitools dependency; stable pattern across all versions of this SDK. | ai | |
| dependencies | unvetted-dep:@applitools/logger | AI (dependencies): First-party Applitools dependency; stable pattern across all versions of this SDK. | ai |
Versions (showing 48 of 48)
| Version | Deps | Published |
|---|---|---|
| 3.60.2 | 11 / 32 | |
| 3.60.1 | 11 / 32 | |
| 3.60.0 | 11 / 32 | |
| 3.59.1 | 11 / 32 | |
| 3.59.0 | 11 / 32 | |
| 3.58.16 | 11 / 32 | |
| 3.58.15 | 11 / 32 | |
| 3.58.14 | 11 / 32 | |
| 3.58.13 | 11 / 32 | |
| 3.58.12 | 11 / 32 | |
| 3.58.11 | 11 / 32 | |
| 3.58.10 | 11 / 32 | |
| 3.58.9 | 11 / 32 | |
| 3.58.8 | 11 / 32 | |
| 3.58.7 | 11 / 32 | |
| 3.58.6 | 11 / 32 | |
| 3.58.5 | 11 / 32 | |
| 3.58.4 | 10 / 32 | |
| 3.58.3 | 10 / 32 | |
| 3.58.2 | 10 / 32 | |
| 3.58.1 | 10 / 32 | |
| 3.58.0 | 10 / 32 | |
| 3.57.3 | 10 / 32 | |
| 3.57.2 | 10 / 32 | |
| 3.57.1 | 10 / 32 | |
| 3.57.0 | 10 / 32 | |
| 3.56.6 | 10 / 32 | |
| 3.56.5 | 10 / 32 | |
| 3.56.4 | 10 / 32 | |
| 3.56.3 | 10 / 32 | |
| 3.56.2 | 10 / 32 | |
| 3.56.1 | 10 / 32 | |
| 3.56.0 | 10 / 32 | |
| 3.55.4 | 10 / 32 | |
| 3.55.3 | 10 / 32 | |
| 3.55.2 | 10 / 32 | |
| 3.55.1 | 10 / 32 | |
| 3.55.0 | 10 / 32 | |
| 3.54.5 | 10 / 32 | |
| 3.54.4 | 10 / 32 | |
| 3.54.3 | 10 / 32 | |
| 3.54.2 | 10 / 32 | |
| 3.54.1 | 10 / 32 | |
| 3.54.0 | 10 / 32 | |
| 3.53.2 | 10 / 32 | |
| 3.53.1 | 10 / 32 | |
| 3.53.0 | 10 / 32 | |
| 3.52.1 | 10 / 31 |
v3.60.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 (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.
v3.60.1
2 findingsThis version was published by a different npm account than previous versions on 2026-05-19. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.60.0
2 findingsThis version was published by a different npm account than previous versions on 2026-05-05. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.59.1
2 findingsThis version was published by a different npm account than previous versions on 2026-05-04. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.59.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.58.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.58.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.58.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.58.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.58.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.58.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.58.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.58.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.58.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.58.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.58.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.58.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.58.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.58.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.58.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.58.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.57.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.57.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.57.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.57.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.56.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.56.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.56.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.56.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.56.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.56.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.
v3.56.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.
v3.55.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.55.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.55.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.55.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.55.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.54.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.54.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.54.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.54.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.54.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.54.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.53.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.53.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.53.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.
v3.52.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.