@applitools/eyes-webdriverio
Applitools Eyes SDK for WebdriverIO
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 |
|---|---|---|---|---|
| publish-pattern | dormant-publish | AI (publish-pattern): Established Applitools org package with 290 versions; dormancy likely reflects release cadence, not takeover. | ai | |
| dependencies | unvetted-dep:@applitools/driver | AI (dependencies): Internal @applitools scoped dep; consistent with this SDK's established dependency pattern. | ai | |
| dependencies | unvetted-dep:@applitools/spec-driver-webdriver | AI (dependencies): Internal @applitools scoped dep; consistent with this SDK's established dependency pattern. | ai | |
| phantom-deps | phantom-dep:@applitools/driver | AI (phantom-deps): Same-org transitive dep; phantom-dep heuristic is a stable false positive for this monorepo package. | ai |
Versions (showing 49 of 149)
| Version | Deps | Published |
|---|---|---|
| 5.45.3 | 3 / 15 | |
| 5.45.2 | 2 / 14 | |
| 5.45.1 | 2 / 14 | |
| 5.45.0 | 2 / 14 | |
| 5.44.19 | 2 / 14 | |
| 5.44.18 | 2 / 14 | |
| 5.44.17 | 2 / 14 | |
| 5.44.16 | 2 / 14 | |
| 5.44.15 | 2 / 14 | |
| 5.44.14 | 2 / 14 | |
| 5.44.13 | 2 / 14 | |
| 5.44.12 | 2 / 14 | |
| 5.44.11 | 2 / 14 | |
| 5.44.10 | 2 / 14 | |
| 5.44.9 | 2 / 14 | |
| 5.44.8 | 2 / 14 | |
| 5.44.7 | 2 / 14 | |
| 5.44.6 | 2 / 14 | |
| 5.44.5 | 2 / 14 | |
| 5.44.4 | 2 / 14 | |
| 5.44.3 | 2 / 14 | |
| 5.44.2 | 2 / 14 | |
| 5.44.1 | 2 / 14 | |
| 5.44.0 | 2 / 14 | |
| 5.43.4 | 2 / 14 | |
| 5.43.3 | 2 / 14 | |
| 5.43.2 | 2 / 14 | |
| 5.43.1 | 2 / 14 | |
| 5.43.0 | 2 / 14 | |
| 5.42.4 | 2 / 14 | |
| 5.42.3 | 2 / 14 | |
| 5.42.2 | 3 / 17 | |
| 5.42.1 | 3 / 17 | |
| 5.42.0 | 3 / 17 | |
| 5.41.1 | 3 / 17 | |
| 5.41.0 | 3 / 31 | |
| 5.40.2 | 3 / 31 | |
| 5.40.1 | 3 / 31 | |
| 5.40.0 | 3 / 31 | |
| 5.39.1 | 3 / 31 | |
| 5.39.0 | 3 / 29 | |
| 5.38.2 | 3 / 29 | |
| 5.38.1 | 3 / 29 | |
| 5.38.0 | 3 / 29 | |
| 5.37.0 | 3 / 29 | |
| 5.36.3 | 3 / 29 | |
| 5.36.2 | 3 / 29 | |
| 5.36.1 | 3 / 29 | |
| 5.36.0 | 3 / 29 |
v5.45.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.45.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.45.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.45.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.44.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.44.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.44.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.44.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.44.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.44.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.44.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.44.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.44.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.44.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.44.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.44.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.44.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.44.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.44.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.44.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.44.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.44.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.44.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.44.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.43.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.43.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.43.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.43.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.43.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.42.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.42.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.42.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.42.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.42.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.41.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.41.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.40.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.40.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.40.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.39.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.39.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.38.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.38.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.38.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.37.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.36.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.36.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.36.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.36.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.