@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 51 of 151)
| Version | Deps | Published |
|---|---|---|
| 1.7.15 | 11 / 8 | |
| 1.7.14 | 11 / 8 | |
| 1.7.13 | 11 / 8 | |
| 1.7.12 | 11 / 8 | |
| 1.7.10 | 11 / 8 | |
| 1.7.9 | 11 / 8 | |
| 1.7.8 | 11 / 8 | |
| 1.7.7 | 11 / 8 | |
| 1.7.6 | 11 / 8 | |
| 1.7.5 | 11 / 8 | |
| 1.7.4 | 11 / 8 | |
| 1.7.3 | 11 / 8 | |
| 1.7.2 | 11 / 8 | |
| 1.7.1 | 11 / 8 | |
| 1.7.0 | 11 / 8 | |
| 1.6.2 | 12 / 8 | |
| 1.6.1 | 12 / 8 | |
| 1.6.0 | 12 / 8 | |
| 1.5.0 | 12 / 8 | |
| 1.4.0 | 12 / 8 | |
| 1.3.0 | 11 / 8 | |
| 1.2.34 | 11 / 8 | |
| 1.2.33 | 11 / 8 | |
| 1.2.32 | 11 / 9 | |
| 1.2.31 | 11 / 9 | |
| 1.2.30 | 11 / 9 | |
| 1.2.29 | 11 / 9 | |
| 1.2.28 | 11 / 9 | |
| 1.2.27 | 11 / 9 | |
| 1.2.26 | 11 / 9 | |
| 1.2.25 | 11 / 9 | |
| 1.2.24 | 11 / 9 | |
| 1.2.23 | 11 / 9 | |
| 1.2.22 | 11 / 9 | |
| 1.2.21 | 11 / 9 | |
| 1.2.20 | 7 / 8 | |
| 1.2.19 | 7 / 8 | |
| 1.2.18 | 7 / 8 | |
| 1.2.17 | 7 / 8 | |
| 1.2.16 | 7 / 8 | |
| 1.2.15 | 7 / 8 | |
| 1.2.14 | 7 / 10 | |
| 1.2.13 | 7 / 10 | |
| 1.2.12 | 7 / 10 | |
| 1.2.11 | 7 / 10 | |
| 1.2.10 | 7 / 10 | |
| 1.2.9 | 7 / 10 | |
| 1.2.8 | 7 / 10 | |
| 1.2.7 | 7 / 10 | |
| 1.2.6 | 7 / 10 | |
| 1.2.5 | 9 / 22 |
v1.7.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.7.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.7.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.7.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.7.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.7.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.7.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.7.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.7.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.7.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.7.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.7.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.7.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.7.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.7.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.6.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.6.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.6.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.5.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.4.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.3.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.2.34
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.2.33
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.2.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.2.31
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.2.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.2.29
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.2.28
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.2.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.2.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.2.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.2.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.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.
v1.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.
v1.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.
v1.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.
v1.2.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.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.
v1.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.
v1.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.
v1.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.
v1.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.
v1.2.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.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.
v1.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.
v1.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.
v1.2.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.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.
v1.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.
v1.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.
v1.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.