@applitools/ufg-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, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:@applitools/jsdom | AI (dependencies): First-party Applitools scoped dependency, not a genuine unvetted third-party package. | ai | |
| provenance | publisher-changed | AI (provenance): movsho is an established Applitools publisher (364 approved packages); transition from danielputerman appears to be a legitimate internal handoff. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Applitools SDK with verified org repo; no suspicious changes in diff; dormancy likely reflects SDK consolidation. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Established monorepo package; missing description is metadata gap, not malware signal. | ai | |
| provenance | no-provenance | AI (provenance): Only ~12% of npm has provenance; not a disqualifier for established packages. | ai | |
| dependencies | unvetted-dep:@applitools/image | AI (dependencies): Internal Applitools monorepo dependency; stable pattern across all versions of this SDK. | ai | |
| dependencies | unvetted-dep:@applitools/logger | AI (dependencies): Internal Applitools monorepo dependency; stable pattern across all versions of this SDK. | ai | |
| dependencies | unvetted-dep:@applitools/utils | AI (dependencies): Internal Applitools monorepo dependency; stable pattern across all versions of this SDK. | ai | |
| dependencies | unvetted-dep:@applitools/req | AI (dependencies): Internal Applitools monorepo dependency; stable pattern across all versions of this SDK. | ai |
Versions (showing 100 of 135)
| Version | Deps | Published |
|---|---|---|
| 1.22.5 | 8 / 6 | |
| 1.22.4 | 8 / 6 | |
| 1.22.3 | 8 / 6 | |
| 1.22.2 | 8 / 6 | |
| 1.22.1 | 8 / 6 | |
| 1.22.0 | 8 / 6 | |
| 1.21.0 | 8 / 6 | |
| 1.20.3 | 8 / 6 | |
| 1.20.2 | 8 / 6 | |
| 1.20.1 | 8 / 6 | |
| 1.20.0 | 8 / 6 | |
| 1.19.4 | 8 / 6 | |
| 1.19.3 | 8 / 6 | |
| 1.19.2 | 8 / 6 | |
| 1.19.1 | 8 / 6 | |
| 1.19.0 | 8 / 6 | |
| 1.18.3 | 8 / 6 | |
| 1.18.2 | 8 / 6 | |
| 1.18.1 | 8 / 6 | |
| 1.18.0 | 8 / 6 | |
| 1.17.5 | 8 / 6 | |
| 1.17.4 | 8 / 6 | |
| 1.17.3 | 8 / 6 | |
| 1.17.2 | 8 / 6 | |
| 1.17.1 | 8 / 6 | |
| 1.17.0 | 8 / 6 | |
| 1.16.14 | 8 / 6 | |
| 1.16.13 | 8 / 6 | |
| 1.16.12 | 8 / 6 | |
| 1.16.11 | 8 / 6 | |
| 1.16.10 | 8 / 6 | |
| 1.16.9 | 8 / 6 | |
| 1.16.8 | 8 / 6 | |
| 1.16.7 | 8 / 6 | |
| 1.16.6 | 8 / 6 | |
| 1.16.5 | 8 / 6 | |
| 1.16.4 | 8 / 6 | |
| 1.16.3 | 8 / 6 | |
| 1.16.2 | 8 / 6 | |
| 1.16.1 | 8 / 6 | |
| 1.16.0 | 8 / 5 | |
| 1.15.1 | 8 / 5 | |
| 1.15.0 | 8 / 5 | |
| 1.14.1 | 8 / 5 | |
| 1.14.0 | 8 / 5 | |
| 1.13.1 | 8 / 5 | |
| 1.13.0 | 8 / 5 | |
| 1.12.3 | 8 / 5 | |
| 1.12.2 | 8 / 5 | |
| 1.12.1 | 8 / 5 | |
| 1.12.0 | 8 / 5 | |
| 1.11.2 | 8 / 5 | |
| 1.11.1 | 8 / 5 | |
| 1.11.0 | 8 / 5 | |
| 1.10.2 | 8 / 5 | |
| 1.9.10 | 8 / 5 | |
| 1.9.9 | 8 / 5 | |
| 1.9.8 | 8 / 5 | |
| 1.9.7 | 8 / 5 | |
| 1.9.6 | 8 / 5 | |
| 1.9.5 | 8 / 6 | |
| 1.9.4 | 8 / 6 | |
| 1.9.3 | 8 / 6 | |
| 1.9.2 | 8 / 6 | |
| 1.9.1 | 8 / 6 | |
| 1.9.0 | 8 / 6 | |
| 1.8.0 | 8 / 6 | |
| 1.7.2 | 8 / 6 | |
| 1.7.1 | 8 / 6 | |
| 1.7.0 | 8 / 6 | |
| 1.6.0 | 8 / 6 | |
| 1.5.3 | 8 / 6 | |
| 1.5.2 | 8 / 6 | |
| 1.5.1 | 8 / 6 | |
| 1.5.0 | 8 / 6 | |
| 1.4.1 | 8 / 6 | |
| 1.4.0 | 8 / 6 | |
| 1.3.0 | 7 / 6 | |
| 1.2.22 | 7 / 6 | |
| 1.2.21 | 7 / 6 | |
| 1.2.20 | 7 / 6 | |
| 1.2.19 | 7 / 6 | |
| 1.2.18 | 7 / 6 | |
| 1.2.17 | 7 / 6 | |
| 1.2.16 | 7 / 6 | |
| 1.2.15 | 7 / 6 | |
| 1.2.12 | 7 / 6 | |
| 1.2.11 | 7 / 6 | |
| 1.2.10 | 7 / 6 | |
| 1.2.9 | 7 / 6 | |
| 1.2.8 | 7 / 6 | |
| 1.2.7 | 7 / 6 | |
| 1.2.6 | 7 / 6 | |
| 1.2.5 | 7 / 5 | |
| 1.2.4 | 7 / 5 | |
| 1.2.3 | 7 / 5 | |
| 1.2.2 | 7 / 5 | |
| 1.2.1 | 7 / 7 | |
| 1.2.0 | 7 / 7 | |
| 1.1.27 | 7 / 7 |
v1.22.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.16.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.16.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.16.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.16.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.16.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.16.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.16.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.16.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.16.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.16.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.15.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.15.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.14.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.14.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.13.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.13.0
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. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.11.2
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.11.1
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.11.0
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.2
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.9.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.
v1.9.9
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.9.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.
v1.9.7
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.9.6
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.9.5
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.9.4
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.9.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.
v1.9.2
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.9.1
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.9.0
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.8.0
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.7.2
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.7.1
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.7.0
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.6.0
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.5.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.
v1.5.2
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.5.1
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.5.0
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.4.1
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.4.0
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.3.0
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.2.22
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.2.21
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.2.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.2.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.2.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.2.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.2.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.2.15
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.2.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.2.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.2.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.
v1.2.9
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.2.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.
v1.2.7
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.2.6
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.2.5
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.2.4
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.2.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.
v1.2.2
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.2.1
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.2.0
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.1.27
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.