@applitools/eyes-selenium
Applitools Eyes SDK for Selenium WebDriver
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 |
|---|---|---|---|---|
| license | uncommon-license:SEE LICENSE IN LICENSE | AI (license): Custom Applitools license; stable for this package. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Long-lived Applitools SDK with 347 versions; dormancy likely reflects release cadence, not takeover. No material changes in diff. | ai | |
| dependencies | unvetted-dep:@applitools/spec-driver-selenium | AI (dependencies): First-party Applitools package; stable dependency pattern across this SDK's many versions. | ai | |
| provenance | no-provenance | AI (provenance): Applitools does not publish with Sigstore provenance; consistent across all versions of this package. | ai |
Versions (showing 42 of 42)
| Version | Deps | Published |
|---|---|---|
| 4.82.43 | 2 / 7 | |
| 4.82.39 | 2 / 7 | |
| 4.82.38 | 2 / 7 | |
| 4.82.37 | 2 / 7 | |
| 4.82.36 | 2 / 7 | |
| 4.82.35 | 2 / 7 | |
| 4.82.34 | 2 / 7 | |
| 4.82.33 | 2 / 7 | |
| 4.82.32 | 2 / 7 | |
| 4.82.31 | 2 / 7 | |
| 4.82.30 | 2 / 7 | |
| 4.82.29 | 2 / 7 | |
| 4.82.28 | 2 / 7 | |
| 4.82.27 | 2 / 7 | |
| 4.82.26 | 2 / 7 | |
| 4.82.25 | 2 / 7 | |
| 4.82.24 | 2 / 7 | |
| 4.82.23 | 2 / 7 | |
| 4.82.22 | 2 / 7 | |
| 4.82.21 | 2 / 7 | |
| 4.82.20 | 2 / 7 | |
| 4.82.19 | 2 / 7 | |
| 4.82.18 | 2 / 7 | |
| 4.82.17 | 2 / 7 | |
| 4.82.16 | 2 / 7 | |
| 4.82.13 | 2 / 7 | |
| 4.82.12 | 2 / 7 | |
| 4.82.11 | 2 / 7 | |
| 4.82.10 | 2 / 7 | |
| 4.82.9 | 2 / 7 | |
| 4.82.8 | 2 / 7 | |
| 4.82.7 | 2 / 7 | |
| 4.82.6 | 2 / 7 | |
| 4.82.5 | 2 / 7 | |
| 4.82.4 | 2 / 7 | |
| 4.82.3 | 2 / 7 | |
| 4.82.2 | 2 / 7 | |
| 4.82.1 | 2 / 7 | |
| 4.82.0 | 2 / 7 | |
| 4.81.4 | 2 / 7 | |
| 4.81.3 | 2 / 7 | |
| 4.81.2 | 2 / 7 |
v4.82.43
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.
v4.82.39
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.82.37
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.82.36
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.82.35
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.82.34
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.82.33
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.82.32
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.82.31
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.82.30
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.82.29
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.82.28
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.82.27
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.82.26
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.82.25
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.82.24
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.82.23
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.82.22
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.82.21
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.82.20
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.82.19
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.82.18
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.82.17
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.82.16
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.82.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.82.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.82.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.82.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.82.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.82.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.82.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.82.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.82.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.82.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.82.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.
v4.82.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.
v4.82.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.
v4.82.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.
v4.81.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.
v4.81.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.
v4.81.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.