@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 35 of 135)
| Version | Deps | Published |
|---|---|---|
| 1.1.26 | 7 / 7 | |
| 1.1.25 | 7 / 7 | |
| 1.1.24 | 7 / 7 | |
| 1.1.23 | 7 / 7 | |
| 1.1.22 | 7 / 18 | |
| 1.1.21 | 7 / 18 | |
| 1.1.19 | 7 / 18 | |
| 1.1.18 | 7 / 18 | |
| 1.1.17 | 7 / 18 | |
| 1.1.16 | 7 / 18 | |
| 1.1.15 | 7 / 18 | |
| 1.1.14 | 7 / 18 | |
| 1.1.13 | 7 / 18 | |
| 1.1.12 | 7 / 18 | |
| 1.1.11 | 7 / 18 | |
| 1.1.10 | 7 / 18 | |
| 1.1.9 | 7 / 18 | |
| 1.1.8 | 7 / 18 | |
| 1.1.7 | 7 / 18 | |
| 1.1.6 | 7 / 18 | |
| 1.1.5 | 7 / 18 | |
| 1.1.4 | 7 / 18 | |
| 1.1.3 | 7 / 18 | |
| 1.1.2 | 7 / 18 | |
| 1.1.1 | 7 / 18 | |
| 1.1.0 | 7 / 18 | |
| 1.0.10 | 7 / 18 | |
| 1.0.9 | 8 / 18 | |
| 1.0.8 | 8 / 18 | |
| 1.0.7 | 8 / 18 | |
| 1.0.5 | 8 / 18 | |
| 1.0.4 | 8 / 18 | |
| 1.0.2 | 8 / 18 | |
| 1.0.1 | 8 / 18 | |
| 1.0.0 | 8 / 18 |
v1.1.26
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.25
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.24
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.23
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.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.1.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.1.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.1.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.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.
v1.1.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.1.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.1.14
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.13
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.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.1.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.1.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.1.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.1.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.1.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.1.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.1.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.1.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.1.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.1.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.1.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.1.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.0.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.0.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.0.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.0.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.0.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.0.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.0.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.0.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.0.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.