@applitools/eyes-playwright
Applitools Eyes SDK for Playwright
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 |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): Established package; provenance is aspirational, not a blocker for mature packages. | ai | |
| license | uncommon-license:SEE LICENSE IN LICENSE | AI (license): Custom license file reference; stable pattern for this package. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Applitools SDK with 185 published versions; dormancy likely reflects release cadence, not account takeover. | ai | |
| dependencies | unvetted-dep:@applitools/req | AI (dependencies): First-party @applitools scoped dep; consistent with Applitools SDK ecosystem. | ai | |
| dependencies | unvetted-dep:@applitools/spec-driver-playwright | AI (dependencies): First-party @applitools scoped dep; Playwright driver for the SDK. | ai | |
| dependencies | unvetted-dep:@applitools/eyes | AI (dependencies): First-party @applitools scoped dep; core SDK dependency. | ai | |
| dependencies | unvetted-dep:@applitools/utils | AI (dependencies): First-party @applitools scoped dep; stable utility package. | ai |
Versions (showing 56 of 156)
| Version | Deps | Published |
|---|---|---|
| 1.23.2 | 2 / 6 | |
| 1.23.1 | 2 / 6 | |
| 1.23.0 | 2 / 6 | |
| 1.22.4 | 2 / 6 | |
| 1.22.3 | 2 / 6 | |
| 1.22.2 | 2 / 6 | |
| 1.22.1 | 2 / 6 | |
| 1.22.0 | 2 / 6 | |
| 1.21.0 | 2 / 6 | |
| 1.20.0 | 2 / 6 | |
| 1.19.1 | 2 / 6 | |
| 1.19.0 | 2 / 6 | |
| 1.18.6 | 2 / 6 | |
| 1.18.5 | 2 / 6 | |
| 1.18.4 | 2 / 6 | |
| 1.18.3 | 2 / 6 | |
| 1.18.2 | 2 / 6 | |
| 1.18.1 | 2 / 6 | |
| 1.18.0 | 2 / 6 | |
| 1.17.22 | 2 / 6 | |
| 1.17.21 | 2 / 6 | |
| 1.17.20 | 2 / 6 | |
| 1.17.19 | 2 / 6 | |
| 1.17.18 | 2 / 6 | |
| 1.17.17 | 2 / 6 | |
| 1.17.16 | 2 / 6 | |
| 1.17.15 | 2 / 6 | |
| 1.17.14 | 2 / 6 | |
| 1.17.13 | 2 / 6 | |
| 1.17.12 | 2 / 6 | |
| 1.17.11 | 2 / 6 | |
| 1.17.10 | 2 / 6 | |
| 1.17.9 | 2 / 6 | |
| 1.17.8 | 2 / 6 | |
| 1.17.7 | 2 / 6 | |
| 1.17.6 | 2 / 6 | |
| 1.17.5 | 2 / 6 | |
| 1.17.4 | 2 / 6 | |
| 1.17.3 | 2 / 6 | |
| 1.17.2 | 2 / 6 | |
| 1.17.1 | 2 / 6 | |
| 1.17.0 | 2 / 6 | |
| 1.16.1 | 2 / 6 | |
| 1.16.0 | 2 / 6 | |
| 1.15.1 | 2 / 6 | |
| 1.15.0 | 2 / 6 | |
| 1.14.1 | 2 / 6 | |
| 1.14.0 | 3 / 9 | |
| 1.13.2 | 3 / 23 | |
| 1.13.1 | 3 / 23 | |
| 1.13.0 | 3 / 23 | |
| 1.12.7 | 3 / 23 | |
| 1.12.6 | 3 / 23 | |
| 1.12.5 | 3 / 23 | |
| 1.12.4 | 3 / 23 | |
| 1.12.3 | 3 / 23 |
v1.23.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.
v1.23.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.
v1.23.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.
v1.22.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.
v1.22.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.
v1.22.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.
v1.22.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.
v1.22.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.
v1.21.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.
v1.20.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.
v1.19.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.
v1.19.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.
v1.18.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.
v1.18.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.
v1.18.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.
v1.18.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.
v1.18.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.
v1.18.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.
v1.18.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.
v1.17.22
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.17.21
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.17.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.
v1.17.19
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.17.18
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.17.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.
v1.17.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.
v1.17.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.
v1.17.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.
v1.17.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.
v1.17.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.
v1.17.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.
v1.17.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.
v1.17.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.
v1.17.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.
v1.17.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.
v1.17.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.
v1.17.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.
v1.17.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.
v1.17.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.
v1.17.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.
v1.17.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.
v1.17.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.
v1.16.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.
v1.16.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.
v1.15.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.
v1.15.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.
v1.14.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.
v1.14.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.
v1.13.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.
v1.13.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.
v1.13.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.
v1.12.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.
v1.12.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.
v1.12.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.
v1.12.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.
v1.12.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.