@applitools/ec-client
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:raw-body | AI (phantom-deps): Likely used indirectly via bundled dist code; established package. | ai | |
| phantom-deps | phantom-dep:proxy-agent | AI (phantom-deps): Likely used indirectly via bundled dist code; established package. | ai | |
| provenance | publisher-changed | AI (provenance): movsho is an established Applitools publisher (94 approved, 0 rejected); internal team transition, not a takeover. | ai | |
| phantom-deps | phantom-dep:webdriver | AI (phantom-deps): webdriver is a declared runtime dependency; phantom-dep heuristic is a false positive for this package. | ai | |
| dependencies | unvetted-dep:@applitools/spec-driver-webdriver | AI (dependencies): Internal Applitools sibling dep; stable pattern across all versions of this package. | ai | |
| dependencies | unvetted-dep:@applitools/socket | AI (dependencies): Internal Applitools sibling dep; stable pattern across all versions of this package. | ai | |
| dependencies | unvetted-dep:@applitools/utils | AI (dependencies): Internal Applitools sibling dep; stable pattern across all versions of this package. | ai | |
| dependencies | unvetted-dep:@applitools/driver | AI (dependencies): Internal Applitools sibling dep; stable pattern across all versions of this package. | ai | |
| dependencies | unvetted-dep:@applitools/logger | AI (dependencies): Internal Applitools sibling dep; stable pattern across all versions of this package. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Applitools SDK package; missing description is cosmetic, not a risk signal for this established org. | ai | |
| provenance | no-provenance | AI (provenance): Applitools packages consistently lack Sigstore provenance; stable false positive for this org. | ai |
Versions (showing 100 of 151)
| Version | Deps | Published |
|---|---|---|
| 1.12.39 | 9 / 9 | |
| 1.12.38 | 9 / 9 | |
| 1.12.37 | 9 / 9 | |
| 1.12.36 | 9 / 9 | |
| 1.12.35 | 9 / 9 | |
| 1.12.34 | 9 / 9 | |
| 1.12.33 | 9 / 9 | |
| 1.12.32 | 9 / 9 | |
| 1.12.31 | 9 / 9 | |
| 1.12.30 | 9 / 9 | |
| 1.12.29 | 9 / 9 | |
| 1.12.28 | 9 / 9 | |
| 1.12.27 | 9 / 9 | |
| 1.12.26 | 9 / 9 | |
| 1.12.25 | 9 / 9 | |
| 1.12.24 | 10 / 9 | |
| 1.12.23 | 10 / 9 | |
| 1.12.22 | 10 / 9 | |
| 1.12.21 | 10 / 9 | |
| 1.12.20 | 11 / 8 | |
| 1.12.19 | 11 / 8 | |
| 1.12.18 | 11 / 8 | |
| 1.12.17 | 11 / 8 | |
| 1.12.16 | 11 / 8 | |
| 1.12.15 | 11 / 8 | |
| 1.12.14 | 11 / 8 | |
| 1.12.13 | 11 / 8 | |
| 1.12.12 | 11 / 8 | |
| 1.12.11 | 11 / 8 | |
| 1.12.10 | 11 / 8 | |
| 1.12.9 | 11 / 8 | |
| 1.12.8 | 11 / 8 | |
| 1.12.7 | 11 / 8 | |
| 1.12.6 | 11 / 8 | |
| 1.12.5 | 11 / 8 | |
| 1.12.4 | 11 / 8 | |
| 1.12.3 | 11 / 8 | |
| 1.12.2 | 11 / 8 | |
| 1.12.1 | 11 / 8 | |
| 1.12.0 | 11 / 8 | |
| 1.11.1 | 11 / 8 | |
| 1.11.0 | 11 / 8 | |
| 1.10.16 | 11 / 8 | |
| 1.10.15 | 11 / 8 | |
| 1.10.14 | 11 / 8 | |
| 1.10.13 | 11 / 8 | |
| 1.10.12 | 11 / 8 | |
| 1.10.11 | 11 / 8 | |
| 1.10.10 | 11 / 8 | |
| 1.10.9 | 11 / 8 | |
| 1.10.8 | 11 / 8 | |
| 1.10.7 | 11 / 8 | |
| 1.10.6 | 11 / 8 | |
| 1.10.5 | 11 / 8 | |
| 1.10.4 | 11 / 8 | |
| 1.10.3 | 11 / 8 | |
| 1.10.2 | 11 / 8 | |
| 1.10.1 | 11 / 8 | |
| 1.10.0 | 11 / 8 | |
| 1.9.18 | 11 / 8 | |
| 1.9.17 | 11 / 8 | |
| 1.9.16 | 11 / 8 | |
| 1.9.15 | 11 / 8 | |
| 1.9.14 | 11 / 8 | |
| 1.9.13 | 11 / 8 | |
| 1.9.12 | 11 / 8 | |
| 1.9.11 | 11 / 8 | |
| 1.9.10 | 11 / 8 | |
| 1.9.9 | 11 / 8 | |
| 1.9.8 | 11 / 8 | |
| 1.9.7 | 11 / 8 | |
| 1.9.6 | 11 / 8 | |
| 1.9.5 | 11 / 8 | |
| 1.9.4 | 11 / 8 | |
| 1.9.3 | 11 / 8 | |
| 1.9.2 | 11 / 8 | |
| 1.9.1 | 11 / 8 | |
| 1.9.0 | 11 / 8 | |
| 1.8.9 | 11 / 8 | |
| 1.8.8 | 11 / 8 | |
| 1.8.7 | 11 / 8 | |
| 1.8.5 | 11 / 8 | |
| 1.8.4 | 11 / 8 | |
| 1.8.3 | 11 / 8 | |
| 1.8.1 | 11 / 8 | |
| 1.8.0 | 11 / 8 | |
| 1.7.32 | 11 / 8 | |
| 1.7.30 | 11 / 8 | |
| 1.7.27 | 11 / 8 | |
| 1.7.26 | 11 / 8 | |
| 1.7.25 | 11 / 8 | |
| 1.7.24 | 11 / 8 | |
| 1.7.23 | 11 / 8 | |
| 1.7.22 | 11 / 8 | |
| 1.7.21 | 11 / 8 | |
| 1.7.20 | 11 / 8 | |
| 1.7.19 | 11 / 8 | |
| 1.7.18 | 11 / 8 | |
| 1.7.17 | 11 / 8 | |
| 1.7.16 | 11 / 8 |
v1.12.39
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.12.38
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.12.37
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.12.36
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.18
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.17
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.16
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.15
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.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.8.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.8.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.8.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.8.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.7.32
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.7.30
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.7.27
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.7.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.
v1.7.25
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.7.24
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.7.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.
v1.7.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.7.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.7.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.7.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.7.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.7.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.7.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.