@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 — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| 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/req | AI (dependencies): Internal Applitools monorepo dependency; stable pattern across all versions of this SDK. | 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/utils | 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 |
Versions (showing 28 of 28)
| Version | Deps | Published |
|---|---|---|
| 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 |
v1.22.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.22.1
2 findingsThis version was published by a different npm account than previous versions on 2026-05-19. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.22.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.20.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
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 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.20.0
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.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.18.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.18.1
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. Only ~12% of npm packages have provenance, so this is common but not ideal.
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. Consider requesting the maintainer enable provenance via CI/CD.
v1.17.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.17.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.17.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.16.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.16.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.16.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.16.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.16.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.