@applitools/core-base
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 |
|---|---|---|---|---|
| publish-pattern | dormant-publish | AI (publish-pattern): Applitools org account publishing to their own established SDK package; no code changes from prior version. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): New maintainer added under the Applitools org umbrella; consistent with internal team management. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Established monorepo package; missing description is benign metadata gap. | ai | |
| provenance | no-provenance | AI (provenance): Provenance adoption is sparse across npm; not a signal for this established package. | ai | |
| dependencies | unvetted-dep:@applitools/req | AI (dependencies): Internal Applitools monorepo dependency; expected for this SDK package. | ai | |
| dependencies | unvetted-dep:@applitools/image | AI (dependencies): Internal Applitools monorepo dependency; expected for this SDK package. | ai | |
| dependencies | unvetted-dep:@applitools/utils | AI (dependencies): Internal Applitools monorepo dependency; expected for this SDK package. | ai | |
| dependencies | unvetted-dep:@applitools/logger | AI (dependencies): Internal Applitools monorepo dependency; expected for this SDK package. | ai |
Versions (showing 100 of 156)
| Version | Deps | Published |
|---|---|---|
| 1.37.0 | 7 / 4 | |
| 1.36.2 | 7 / 4 | |
| 1.36.1 | 7 / 4 | |
| 1.36.0 | 7 / 4 | |
| 1.35.3 | 7 / 4 | |
| 1.35.2 | 7 / 4 | |
| 1.35.1 | 7 / 4 | |
| 1.35.0 | 7 / 4 | |
| 1.34.1 | 7 / 4 | |
| 1.33.0 | 6 / 4 | |
| 1.32.5 | 6 / 4 | |
| 1.32.4 | 6 / 4 | |
| 1.32.3 | 6 / 4 | |
| 1.32.2 | 6 / 4 | |
| 1.32.1 | 6 / 4 | |
| 1.32.0 | 6 / 4 | |
| 1.31.3 | 6 / 4 | |
| 1.31.2 | 6 / 4 | |
| 1.31.1 | 6 / 4 | |
| 1.31.0 | 6 / 4 | |
| 1.30.1 | 6 / 4 | |
| 1.30.0 | 6 / 4 | |
| 1.29.0 | 6 / 4 | |
| 1.28.2 | 6 / 4 | |
| 1.28.1 | 6 / 4 | |
| 1.28.0 | 6 / 4 | |
| 1.27.4 | 6 / 4 | |
| 1.27.3 | 6 / 4 | |
| 1.27.2 | 6 / 4 | |
| 1.27.1 | 6 / 4 | |
| 1.27.0 | 6 / 4 | |
| 1.26.0 | 6 / 4 | |
| 1.25.6 | 6 / 4 | |
| 1.25.5 | 6 / 4 | |
| 1.25.4 | 6 / 4 | |
| 1.25.3 | 6 / 4 | |
| 1.25.2 | 6 / 4 | |
| 1.25.1 | 6 / 4 | |
| 1.25.0 | 6 / 4 | |
| 1.24.0 | 6 / 4 | |
| 1.23.0 | 6 / 4 | |
| 1.22.3 | 6 / 4 | |
| 1.22.2 | 6 / 4 | |
| 1.22.1 | 6 / 4 | |
| 1.22.0 | 6 / 4 | |
| 1.21.1 | 6 / 4 | |
| 1.21.0 | 6 / 4 | |
| 1.20.0 | 6 / 4 | |
| 1.19.3 | 6 / 4 | |
| 1.19.2 | 6 / 4 | |
| 1.19.1 | 6 / 4 | |
| 1.19.0 | 6 / 4 | |
| 1.18.0 | 6 / 4 | |
| 1.17.2 | 6 / 4 | |
| 1.17.1 | 6 / 4 | |
| 1.17.0 | 7 / 4 | |
| 1.16.1 | 6 / 4 | |
| 1.16.0 | 6 / 4 | |
| 1.15.2 | 6 / 4 | |
| 1.15.1 | 6 / 4 | |
| 1.14.0 | 6 / 4 | |
| 1.13.0 | 6 / 4 | |
| 1.12.1 | 6 / 4 | |
| 1.11.1 | 6 / 4 | |
| 1.11.0 | 6 / 4 | |
| 1.10.1 | 6 / 4 | |
| 1.9.1 | 6 / 4 | |
| 1.9.0 | 6 / 4 | |
| 1.8.0 | 6 / 4 | |
| 1.7.5 | 6 / 4 | |
| 1.7.4 | 6 / 4 | |
| 1.7.3 | 6 / 4 | |
| 1.7.2 | 6 / 4 | |
| 1.7.1 | 6 / 4 | |
| 1.7.0 | 6 / 4 | |
| 1.6.1 | 6 / 4 | |
| 1.6.0 | 6 / 4 | |
| 1.5.3 | 6 / 4 | |
| 1.5.2 | 6 / 4 | |
| 1.5.1 | 6 / 4 | |
| 1.5.0 | 6 / 4 | |
| 1.4.3 | 6 / 4 | |
| 1.4.2 | 6 / 4 | |
| 1.4.1 | 6 / 4 | |
| 1.4.0 | 6 / 4 | |
| 1.3.0 | 6 / 4 | |
| 1.2.1 | 6 / 4 | |
| 1.2.0 | 6 / 4 | |
| 1.1.58 | 6 / 4 | |
| 1.1.57 | 6 / 4 | |
| 1.1.56 | 6 / 5 | |
| 1.1.55 | 6 / 5 | |
| 1.1.54 | 6 / 5 | |
| 1.1.53 | 6 / 5 | |
| 1.1.52 | 6 / 5 | |
| 1.1.51 | 6 / 5 | |
| 1.1.50 | 6 / 5 | |
| 1.1.49 | 6 / 5 | |
| 1.1.48 | 6 / 5 | |
| 1.1.47 | 6 / 5 |
v1.37.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.36.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.36.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.36.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.24.0
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (noam.gaash) than the most recent previously approved version (applitools-admin) on 2025-04-13, but noam.gaash is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v1.23.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.22.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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
1 finding[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.21.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.21.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.20.0
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.0
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.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.2
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.14.0
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. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.12.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.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.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.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.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.7.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.7.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.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.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.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.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.4.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.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.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.58
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.57
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.56
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.55
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.54
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.53
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.52
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.51
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.50
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.49
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.48
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.47
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.