@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 — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| 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/driver | 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/spec-driver-webdriver | 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 | |
| dependencies | unvetted-dep:@applitools/utils | 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 41 of 41)
| Version | Deps | Published |
|---|---|---|
| 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 |
v1.12.31
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.12.30
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.12.29
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.12.28
2 findingsThis version was published by a different npm account than previous versions on 2026-05-05. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.12.27
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2026-05-04. This could indicate a legitimate maintainer transition or an account compromise.
v1.12.26
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.12.25
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.12.24
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.12.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.12.22
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.12.21
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.12.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.12.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.12.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.12.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.12.16
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.12.15
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.12.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.12.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.12.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.12.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.12.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.12.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.12.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.12.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.12.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.12.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.12.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.12.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.12.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.12.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.12.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.11.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.11.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.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.10.15
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.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.10.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.10.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.10.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.