@applitools/eyes
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 |
|---|---|---|---|---|
| license | uncommon-license:SEE LICENSE IN LICENSE | AI (license): Custom license reference; legitimate for established org packages. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Established Applitools package with matching official repo; no suspicious changes in this release. | ai | |
| dependencies | unvetted-dep:@applitools/utils | AI (dependencies): Internal Applitools monorepo dependency; expected for this SDK family. | ai | |
| dependencies | unvetted-dep:@applitools/logger | AI (dependencies): Internal Applitools monorepo dependency; expected for this SDK family. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Applitools SDK package; missing description is cosmetic, not a malware indicator for this established package. | ai |
Versions (showing 100 of 175)
| Version | Deps | Published |
|---|---|---|
| 1.44.0 | 5 / 3 | |
| 1.43.7 | 5 / 3 | |
| 1.43.6 | 5 / 3 | |
| 1.43.5 | 5 / 3 | |
| 1.43.4 | 5 / 3 | |
| 1.43.3 | 5 / 3 | |
| 1.43.2 | 5 / 3 | |
| 1.43.0 | 5 / 3 | |
| 1.42.1 | 5 / 3 | |
| 1.40.1 | 5 / 2 | |
| 1.40.0 | 5 / 2 | |
| 1.39.0 | 5 / 2 | |
| 1.38.15 | 5 / 2 | |
| 1.38.14 | 5 / 2 | |
| 1.38.13 | 5 / 2 | |
| 1.38.12 | 5 / 2 | |
| 1.38.11 | 5 / 2 | |
| 1.38.10 | 5 / 2 | |
| 1.38.9 | 5 / 2 | |
| 1.38.8 | 5 / 2 | |
| 1.38.7 | 5 / 2 | |
| 1.38.6 | 5 / 2 | |
| 1.38.5 | 5 / 2 | |
| 1.38.4 | 5 / 2 | |
| 1.38.3 | 5 / 2 | |
| 1.38.2 | 5 / 2 | |
| 1.38.1 | 5 / 2 | |
| 1.38.0 | 5 / 2 | |
| 1.37.0 | 5 / 2 | |
| 1.36.20 | 5 / 2 | |
| 1.36.19 | 5 / 2 | |
| 1.36.18 | 5 / 2 | |
| 1.36.17 | 5 / 2 | |
| 1.36.16 | 5 / 2 | |
| 1.36.15 | 5 / 2 | |
| 1.36.14 | 5 / 2 | |
| 1.36.13 | 5 / 2 | |
| 1.36.12 | 5 / 2 | |
| 1.36.11 | 5 / 2 | |
| 1.36.10 | 5 / 2 | |
| 1.36.9 | 5 / 2 | |
| 1.36.8 | 5 / 2 | |
| 1.36.7 | 5 / 2 | |
| 1.36.6 | 5 / 2 | |
| 1.36.5 | 5 / 2 | |
| 1.36.4 | 5 / 2 | |
| 1.36.3 | 5 / 2 | |
| 1.36.2 | 5 / 2 | |
| 1.36.1 | 5 / 2 | |
| 1.36.0 | 5 / 2 | |
| 1.35.3 | 5 / 2 | |
| 1.35.2 | 5 / 2 | |
| 1.35.1 | 5 / 2 | |
| 1.35.0 | 5 / 2 | |
| 1.34.6 | 5 / 2 | |
| 1.34.5 | 5 / 2 | |
| 1.34.4 | 5 / 2 | |
| 1.34.3 | 5 / 2 | |
| 1.34.2 | 5 / 2 | |
| 1.34.1 | 5 / 2 | |
| 1.34.0 | 5 / 2 | |
| 1.33.4 | 4 / 2 | |
| 1.33.2 | 4 / 2 | |
| 1.33.1 | 4 / 2 | |
| 1.33.0 | 4 / 2 | |
| 1.32.7 | 4 / 2 | |
| 1.32.6 | 4 / 2 | |
| 1.32.5 | 4 / 2 | |
| 1.32.4 | 4 / 2 | |
| 1.32.3 | 4 / 2 | |
| 1.32.2 | 4 / 2 | |
| 1.32.1 | 4 / 2 | |
| 1.32.0 | 4 / 2 | |
| 1.31.3 | 4 / 2 | |
| 1.31.2 | 4 / 2 | |
| 1.31.1 | 4 / 2 | |
| 1.31.0 | 4 / 2 | |
| 1.30.0 | 4 / 2 | |
| 1.29.4 | 4 / 2 | |
| 1.29.3 | 4 / 2 | |
| 1.29.2 | 4 / 2 | |
| 1.29.1 | 4 / 2 | |
| 1.29.0 | 4 / 2 | |
| 1.28.0 | 3 / 2 | |
| 1.27.0 | 3 / 2 | |
| 1.26.4 | 3 / 2 | |
| 1.26.3 | 3 / 2 | |
| 1.26.2 | 3 / 2 | |
| 1.26.1 | 3 / 2 | |
| 1.26.0 | 3 / 2 | |
| 1.25.1 | 3 / 2 | |
| 1.25.0 | 3 / 2 | |
| 1.24.0 | 3 / 2 | |
| 1.23.2 | 3 / 2 | |
| 1.23.1 | 3 / 2 | |
| 1.23.0 | 3 / 2 | |
| 1.22.2 | 3 / 2 | |
| 1.22.1 | 3 / 2 | |
| 1.22.0 | 3 / 2 | |
| 1.21.0 | 3 / 2 |
v1.44.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.43.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.43.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.43.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.34.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.33.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.33.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.33.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.33.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.32.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.32.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.32.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.32.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.32.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.32.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.32.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.32.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.31.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.31.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.31.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.31.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.30.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.29.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.29.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.29.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.29.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.29.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.28.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.27.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.26.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.26.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.26.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.26.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.26.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.25.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.25.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.24.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.23.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.23.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.23.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.22.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.22.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.22.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.21.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.