@applitools/eyes-testcafe
Applitools Eyes SDK for TestCafe
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 | publisher-changed | AI (provenance): danielputerman is a long-standing Applitools org member (2337 days, 404 approved packages); transition appears legitimate. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Long-lived Applitools org package; inactivity gap consistent with SDK maintenance cycles, not account takeover. | ai | |
| dependencies | unvetted-dep:@applitools/utils | AI (dependencies): Internal Applitools org dependency; consistent with established monorepo pattern across all versions. | ai | |
| dependencies | unvetted-dep:@applitools/driver | AI (dependencies): Internal Applitools org dependency; consistent with established monorepo pattern across all versions. | ai | |
| phantom-deps | phantom-dep:@applitools/driver | AI (phantom-deps): Same-org sibling dep; phantom-dep heuristic is a stable false positive for this monorepo package. | ai | |
| provenance | no-provenance | AI (provenance): Applitools does not publish with Sigstore provenance; consistent across all versions of this package. | ai |
Versions (showing 79 of 79)
| Version | Deps | Published |
|---|---|---|
| 6.3.52 | 3 / 6 | |
| 6.3.51 | 3 / 6 | |
| 6.3.50 | 3 / 6 | |
| 6.3.49 | 3 / 6 | |
| 6.3.48 | 3 / 6 | |
| 6.3.47 | 3 / 6 | |
| 6.3.46 | 3 / 6 | |
| 6.3.45 | 3 / 6 | |
| 6.3.44 | 3 / 6 | |
| 6.3.43 | 3 / 6 | |
| 6.3.42 | 3 / 6 | |
| 6.3.41 | 3 / 6 | |
| 6.3.40 | 3 / 6 | |
| 6.3.39 | 3 / 6 | |
| 6.3.38 | 3 / 6 | |
| 6.3.37 | 3 / 6 | |
| 6.3.36 | 3 / 6 | |
| 6.3.35 | 3 / 6 | |
| 6.3.34 | 3 / 6 | |
| 6.3.33 | 3 / 6 | |
| 6.3.32 | 3 / 6 | |
| 6.3.31 | 3 / 6 | |
| 6.3.30 | 3 / 6 | |
| 6.3.29 | 3 / 6 | |
| 6.3.28 | 3 / 6 | |
| 6.3.27 | 3 / 6 | |
| 6.3.26 | 3 / 6 | |
| 6.3.25 | 3 / 6 | |
| 6.3.24 | 3 / 6 | |
| 6.3.23 | 3 / 6 | |
| 6.3.22 | 3 / 6 | |
| 6.3.21 | 3 / 6 | |
| 6.3.20 | 3 / 6 | |
| 6.3.19 | 3 / 6 | |
| 6.3.18 | 3 / 6 | |
| 6.3.17 | 3 / 6 | |
| 6.3.16 | 3 / 6 | |
| 6.3.15 | 3 / 6 | |
| 6.3.14 | 3 / 6 | |
| 6.3.13 | 3 / 6 | |
| 6.3.12 | 3 / 6 | |
| 6.3.11 | 3 / 6 | |
| 6.3.10 | 3 / 6 | |
| 6.3.9 | 3 / 6 | |
| 6.3.8 | 3 / 6 | |
| 6.3.7 | 3 / 6 | |
| 6.3.6 | 3 / 6 | |
| 6.3.5 | 3 / 6 | |
| 6.3.4 | 3 / 6 | |
| 6.3.3 | 3 / 6 | |
| 6.3.2 | 3 / 6 | |
| 6.3.1 | 3 / 6 | |
| 6.3.0 | 3 / 6 | |
| 6.2.26 | 3 / 6 | |
| 6.2.25 | 3 / 6 | |
| 6.2.24 | 3 / 6 | |
| 6.2.23 | 3 / 6 | |
| 6.2.22 | 3 / 6 | |
| 6.2.21 | 3 / 6 | |
| 6.2.20 | 3 / 6 | |
| 6.2.18 | 3 / 6 | |
| 6.2.17 | 3 / 6 | |
| 6.2.16 | 3 / 6 | |
| 6.2.15 | 3 / 6 | |
| 6.2.14 | 3 / 6 | |
| 6.2.12 | 3 / 6 | |
| 6.2.11 | 3 / 6 | |
| 6.2.10 | 3 / 6 | |
| 6.2.8 | 3 / 6 | |
| 6.2.7 | 3 / 6 | |
| 6.2.6 | 3 / 6 | |
| 6.2.5 | 3 / 6 | |
| 6.2.4 | 3 / 6 | |
| 6.2.2 | 3 / 6 | |
| 6.2.1 | 3 / 6 | |
| 6.2.0 | 3 / 6 | |
| 6.1.1 | 3 / 6 | |
| 6.0.3 | 3 / 6 | |
| 6.0.0 | 3 / 6 |
v6.3.52
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.3.51
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.3.50
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.3.49
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.2.23
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.2.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.
v6.2.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.
v6.2.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.
v6.2.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.
v6.2.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.
v6.2.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.
v6.2.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.
v6.2.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.
v6.2.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.
v6.2.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.
v6.2.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.
v6.2.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.
v6.2.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.
v6.2.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.
v6.2.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.
v6.2.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.
v6.2.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.
v6.2.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.
v6.2.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.
v6.1.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.
v6.0.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.
v6.0.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.