@applitools/core
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@types/ws | AI (phantom-deps): Framework-scoped type definitions loaded by convention; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:webdriver | AI (phantom-deps): Referenced in config; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:@applitools/socket | AI (phantom-deps): Same-org scope dep; phantom-dep heuristic is a stable false positive for this monorepo package. | ai | |
| typosquat | typosquat.levenshtein:cors | AI (typosquat): Scoped @applitools/core is a legitimate SDK package; Levenshtein match to 'cors' is a false positive. | ai |
Versions (showing 100 of 144)
| Version | Deps | Published |
|---|---|---|
| 4.67.0 | 19 / 25 | |
| 4.66.2 | 19 / 25 | |
| 4.66.1 | 19 / 25 | |
| 4.66.0 | 19 / 25 | |
| 4.65.2 | 18 / 24 | |
| 4.65.1 | 18 / 24 | |
| 4.65.0 | 18 / 24 | |
| 4.64.1 | 18 / 24 | |
| 4.64.0 | 18 / 23 | |
| 4.63.1 | 18 / 23 | |
| 4.62.0 | 18 / 18 | |
| 4.61.0 | 18 / 16 | |
| 4.60.0 | 18 / 16 | |
| 4.59.3 | 18 / 16 | |
| 4.59.2 | 18 / 16 | |
| 4.59.1 | 18 / 16 | |
| 4.59.0 | 18 / 16 | |
| 4.58.2 | 18 / 16 | |
| 4.58.1 | 18 / 16 | |
| 4.58.0 | 18 / 16 | |
| 4.57.2 | 18 / 16 | |
| 4.57.1 | 18 / 16 | |
| 4.57.0 | 18 / 16 | |
| 4.56.3 | 18 / 16 | |
| 4.56.2 | 23 / 17 | |
| 4.56.1 | 23 / 18 | |
| 4.56.0 | 23 / 18 | |
| 4.55.0 | 23 / 18 | |
| 4.54.4 | 23 / 18 | |
| 4.54.3 | 23 / 18 | |
| 4.54.2 | 23 / 18 | |
| 4.54.1 | 23 / 18 | |
| 4.54.0 | 23 / 18 | |
| 4.53.2 | 23 / 18 | |
| 4.53.1 | 23 / 18 | |
| 4.53.0 | 23 / 18 | |
| 4.52.0 | 23 / 18 | |
| 4.51.0 | 23 / 18 | |
| 4.50.4 | 23 / 18 | |
| 4.50.3 | 23 / 18 | |
| 4.50.2 | 23 / 18 | |
| 4.50.1 | 23 / 18 | |
| 4.50.0 | 23 / 18 | |
| 4.49.0 | 23 / 18 | |
| 4.48.0 | 23 / 18 | |
| 4.47.1 | 23 / 18 | |
| 4.47.0 | 23 / 18 | |
| 4.46.0 | 23 / 18 | |
| 4.45.0 | 23 / 18 | |
| 4.44.5 | 23 / 18 | |
| 4.44.4 | 23 / 18 | |
| 4.44.3 | 23 / 18 | |
| 4.44.2 | 23 / 18 | |
| 4.44.1 | 23 / 18 | |
| 4.44.0 | 23 / 18 | |
| 4.43.0 | 23 / 18 | |
| 4.42.1 | 23 / 18 | |
| 4.42.0 | 23 / 18 | |
| 4.41.0 | 23 / 18 | |
| 4.40.0 | 23 / 18 | |
| 4.39.3 | 23 / 18 | |
| 4.39.2 | 23 / 18 | |
| 4.39.1 | 23 / 18 | |
| 4.39.0 | 23 / 18 | |
| 4.38.2 | 23 / 17 | |
| 4.38.1 | 23 / 17 | |
| 4.38.0 | 23 / 17 | |
| 4.37.1 | 23 / 17 | |
| 4.37.0 | 23 / 17 | |
| 4.36.0 | 23 / 17 | |
| 4.35.1 | 22 / 16 | |
| 4.35.0 | 22 / 16 | |
| 4.34.0 | 22 / 16 | |
| 4.33.0 | 22 / 16 | |
| 4.32.2 | 22 / 16 | |
| 4.32.1 | 22 / 16 | |
| 4.32.0 | 22 / 16 | |
| 4.31.4 | 22 / 16 | |
| 4.31.3 | 22 / 16 | |
| 4.31.2 | 22 / 16 | |
| 4.31.1 | 22 / 16 | |
| 4.31.0 | 22 / 16 | |
| 4.30.1 | 22 / 16 | |
| 4.30.0 | 22 / 16 | |
| 4.29.1 | 22 / 16 | |
| 4.29.0 | 22 / 15 | |
| 4.28.0 | 22 / 15 | |
| 4.27.1 | 22 / 15 | |
| 4.27.0 | 22 / 15 | |
| 4.26.0 | 22 / 15 | |
| 4.25.0 | 22 / 15 | |
| 4.24.2 | 22 / 15 | |
| 4.24.1 | 22 / 15 | |
| 4.24.0 | 22 / 15 | |
| 4.23.1 | 22 / 15 | |
| 4.23.0 | 22 / 15 | |
| 4.22.1 | 22 / 15 | |
| 4.22.0 | 22 / 15 | |
| 4.21.2 | 22 / 15 | |
| 4.21.1 | 22 / 15 |
v4.67.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.66.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.66.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.66.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.37.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.36.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.35.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.35.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.34.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.33.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.32.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.32.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.32.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.31.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.31.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.31.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.31.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.31.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.30.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.30.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.29.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.29.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.28.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.27.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.27.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.26.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.25.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.24.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.24.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.24.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.23.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.23.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.22.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.22.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.21.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.21.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.