@applitools/driver
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 verified long-standing Applitools contributor with 360 approved packages and no rejections. | ai | |
| dependencies | unvetted-dep:@applitools/logger | AI (dependencies): First-party Applitools dependency; stable pattern across all versions of this package. | ai | |
| provenance | no-provenance | AI (provenance): Applitools packages consistently publish without Sigstore provenance; stable pattern across all versions. | ai |
Versions (showing 49 of 49)
| Version | Deps | Published |
|---|---|---|
| 1.26.6 | 4 / 1 | |
| 1.26.5 | 4 / 1 | |
| 1.26.4 | 4 / 1 | |
| 1.26.3 | 4 / 1 | |
| 1.26.2 | 4 / 1 | |
| 1.26.1 | 4 / 1 | |
| 1.26.0 | 4 / 1 | |
| 1.25.5 | 4 / 1 | |
| 1.25.4 | 4 / 1 | |
| 1.25.3 | 4 / 1 | |
| 1.25.2 | 4 / 1 | |
| 1.25.1 | 4 / 1 | |
| 1.25.0 | 4 / 1 | |
| 1.24.4 | 4 / 1 | |
| 1.24.3 | 4 / 1 | |
| 1.24.2 | 4 / 1 | |
| 1.24.1 | 4 / 1 | |
| 1.24.0 | 4 / 1 | |
| 1.23.5 | 4 / 1 | |
| 1.23.4 | 4 / 1 | |
| 1.23.3 | 4 / 1 | |
| 1.23.2 | 4 / 1 | |
| 1.23.1 | 4 / 1 | |
| 1.23.0 | 4 / 1 | |
| 1.22.1 | 4 / 1 | |
| 1.22.0 | 4 / 1 | |
| 1.21.4 | 4 / 1 | |
| 1.21.3 | 4 / 1 | |
| 1.21.2 | 4 / 1 | |
| 1.21.1 | 4 / 1 | |
| 1.21.0 | 4 / 1 | |
| 1.20.5 | 4 / 1 | |
| 1.20.4 | 4 / 1 | |
| 1.20.3 | 4 / 1 | |
| 1.20.2 | 4 / 1 | |
| 1.20.1 | 4 / 1 | |
| 1.20.0 | 4 / 1 | |
| 1.19.7 | 4 / 1 | |
| 1.19.6 | 4 / 1 | |
| 1.19.5 | 4 / 1 | |
| 1.19.4 | 4 / 1 | |
| 1.19.3 | 4 / 1 | |
| 1.19.2 | 4 / 1 | |
| 1.19.1 | 4 / 1 | |
| 1.19.0 | 4 / 1 | |
| 1.18.0 | 4 / 1 | |
| 1.17.5 | 4 / 1 | |
| 1.17.4 | 4 / 1 | |
| 1.17.3 | 4 / 1 |
v1.26.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.26.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.21.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.21.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.21.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.21.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.21.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.20.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.20.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.20.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.20.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.20.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.20.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.19.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.19.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.19.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.19.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.19.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.19.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.19.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.19.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.18.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.17.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.17.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.17.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.