@applitools/socket
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 | no-provenance | AI (provenance): Applitools org packages consistently lack Sigstore provenance; stable false positive for this package family. | ai |
Versions (showing 26 of 26)
| Version | Deps | Published |
|---|---|---|
| 1.3.15 | 2 / 1 | |
| 1.3.14 | 2 / 1 | |
| 1.3.13 | 2 / 1 | |
| 1.3.12 | 2 / 1 | |
| 1.3.11 | 2 / 1 | |
| 1.3.10 | 2 / 1 | |
| 1.3.9 | 2 / 1 | |
| 1.3.8 | 2 / 1 | |
| 1.3.7 | 2 / 1 | |
| 1.3.5 | 2 / 1 | |
| 1.3.4 | 2 / 1 | |
| 1.3.3 | 2 / 1 | |
| 1.3.2 | 2 / 1 | |
| 1.3.1 | 2 / 1 | |
| 1.3.0 | 2 / 1 | |
| 1.2.6 | 2 / 1 | |
| 1.2.5 | 2 / 1 | |
| 1.2.4 | 2 / 1 | |
| 1.2.3 | 2 / 1 | |
| 1.2.2 | 2 / 1 | |
| 1.2.1 | 2 / 1 | |
| 1.2.0 | 2 / 1 | |
| 1.1.20 | 2 / 1 | |
| 1.1.19 | 2 / 1 | |
| 1.1.18 | 2 / 1 | |
| 1.1.17 | 2 / 1 |
v1.3.15
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.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. Only ~12% of npm packages have provenance, so this is common but not ideal.