@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, 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 |
|---|---|---|---|---|
| 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 35 of 135)
| Version | Deps | Published |
|---|---|---|
| 4.66.15 | 2 / 8 | |
| 4.66.14 | 2 / 8 | |
| 4.66.13 | 2 / 8 | |
| 4.66.12 | 2 / 8 | |
| 4.66.11 | 2 / 8 | |
| 4.66.10 | 2 / 8 | |
| 4.66.9 | 2 / 8 | |
| 4.66.8 | 2 / 8 | |
| 4.66.7 | 2 / 8 | |
| 4.66.6 | 2 / 8 | |
| 4.66.5 | 2 / 8 | |
| 4.66.4 | 2 / 8 | |
| 4.66.3 | 2 / 8 | |
| 4.66.2 | 2 / 8 | |
| 4.66.1 | 2 / 8 | |
| 4.66.0 | 2 / 8 | |
| 4.65.6 | 2 / 8 | |
| 4.65.5 | 2 / 8 | |
| 4.65.4 | 2 / 8 | |
| 4.65.3 | 2 / 8 | |
| 4.65.2 | 2 / 8 | |
| 4.65.1 | 2 / 8 | |
| 4.65.0 | 2 / 8 | |
| 4.64.1 | 2 / 8 | |
| 4.64.0 | 3 / 10 | |
| 4.63.1 | 3 / 23 | |
| 4.63.0 | 3 / 23 | |
| 4.62.1 | 3 / 23 | |
| 4.62.0 | 3 / 23 | |
| 4.61.0 | 3 / 23 | |
| 4.60.2 | 3 / 23 | |
| 4.60.1 | 3 / 23 | |
| 4.60.0 | 3 / 23 | |
| 4.59.6 | 3 / 23 | |
| 4.59.5 | 3 / 23 |
v4.66.15
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.66.14
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.66.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.66.12
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.66.11
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.66.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.66.9
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.66.8
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.66.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.66.6
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.66.5
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.66.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.66.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.66.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.66.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.66.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.65.6
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.65.5
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.65.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.65.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.65.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.65.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.65.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.64.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.64.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.63.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.63.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.62.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.62.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.61.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.60.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.60.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.60.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.59.6
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.59.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.