@applitools/spec-driver-webdriver
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 |
|---|---|---|---|---|
| npm-metadata | no-description | AI (npm-metadata): Applitools monorepo package; missing description is a consistent pattern, not a malice indicator. | ai | |
| provenance | no-provenance | AI (provenance): Established Applitools SDK; no provenance is consistent across their entire package family. | ai |
Versions (showing 50 of 50)
| Version | Deps | Published |
|---|---|---|
| 1.6.6 | 4 / 7 | |
| 1.6.5 | 4 / 7 | |
| 1.6.4 | 4 / 7 | |
| 1.6.3 | 4 / 7 | |
| 1.6.2 | 4 / 7 | |
| 1.6.1 | 4 / 7 | |
| 1.6.0 | 4 / 6 | |
| 1.5.10 | 4 / 6 | |
| 1.5.9 | 4 / 6 | |
| 1.5.8 | 4 / 6 | |
| 1.5.7 | 4 / 6 | |
| 1.5.6 | 4 / 6 | |
| 1.5.5 | 4 / 6 | |
| 1.5.3 | 4 / 6 | |
| 1.5.2 | 4 / 6 | |
| 1.5.0 | 4 / 6 | |
| 1.4.5 | 4 / 6 | |
| 1.4.4 | 4 / 6 | |
| 1.4.3 | 4 / 6 | |
| 1.4.2 | 4 / 6 | |
| 1.4.1 | 4 / 6 | |
| 1.4.0 | 4 / 6 | |
| 1.3.1 | 4 / 6 | |
| 1.3.0 | 4 / 6 | |
| 1.2.6 | 4 / 6 | |
| 1.2.5 | 4 / 6 | |
| 1.2.4 | 4 / 6 | |
| 1.2.3 | 4 / 6 | |
| 1.2.2 | 4 / 6 | |
| 1.2.1 | 4 / 6 | |
| 1.2.0 | 4 / 6 | |
| 1.1.26 | 4 / 6 | |
| 1.1.25 | 4 / 6 | |
| 1.1.24 | 4 / 6 | |
| 1.1.23 | 4 / 6 | |
| 1.1.22 | 4 / 6 | |
| 1.1.21 | 4 / 6 | |
| 1.1.20 | 4 / 6 | |
| 1.1.19 | 4 / 6 | |
| 1.1.18 | 4 / 6 | |
| 1.1.17 | 4 / 6 | |
| 1.1.16 | 4 / 6 | |
| 1.1.15 | 4 / 6 | |
| 1.1.14 | 4 / 6 | |
| 1.1.13 | 4 / 6 | |
| 1.1.12 | 4 / 6 | |
| 1.1.11 | 4 / 6 | |
| 1.1.10 | 4 / 6 | |
| 1.1.9 | 4 / 6 | |
| 1.1.8 | 4 / 6 |
v1.6.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.26
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.25
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.24
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.23
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.22
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.21
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.20
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.19
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.18
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.17
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.16
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.15
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.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.