← Home

@applitools/core-universal

npm Repository Homepage
18
Versions
SEE LICENSE IN LICENSE
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

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

danielputermangearmamit.rokachroy.selaapplitools-adminapplitools-readonlyiasisappnoam.mendelarik-applitoolsyotammademdenis.styrtkyrylo.onufriievormedaclementbarryidosapplitoolsgofilordalex.burdeynyyronikar_applitoolsbenny.halberstadtgrayscale64fatihsolhan-applitoolsitaiz134dockermasteranandbagmarsergovapplitoolsfluxomni.iommilappnoam.gaashroeefranastasia.koifmanaretm_borodavkayonittzairilevyasundaram-applitoolsamir.groismanemasuarynaama.shohamadamcarmimulygottliebyoavnaveh-applitoolschaimaharonsonmovshonetta.bondyshirbinranhadardmytro-hrostyslav.pidburachynskyi.applitoolstaltool

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
npm-metadata no-description AI (npm-metadata): Established Applitools SDK package; missing description is a cosmetic issue, not a malice indicator. ai
provenance publisher-changed AI (provenance): movsho is an established Applitools publisher (396 approved packages); transition appears to be an internal org handoff. ai
dependencies unvetted-dep:@applitools/driver AI (dependencies): First-party Applitools sibling package; stable pattern across versions. ai
dependencies unvetted-dep:@applitools/logger AI (dependencies): First-party Applitools sibling package; stable pattern across versions. ai
dependencies unvetted-dep:@applitools/utils AI (dependencies): First-party Applitools sibling package; stable pattern across versions. ai
dependencies unvetted-dep:@applitools/socket AI (dependencies): First-party Applitools sibling package; stable pattern across versions. ai
dependencies unvetted-dep:@applitools/spec-driver-webdriver AI (dependencies): First-party Applitools sibling package; stable pattern across versions. ai
phantom-deps phantom-dep:@types/ws AI (phantom-deps): @types/ws is a type declaration dep; not directly imported at runtime by design. ai
phantom-deps phantom-dep:chalk AI (phantom-deps): chalk is a declared runtime dep used in CLI tooling; phantom-dep heuristic false positive for this package. ai
phantom-deps phantom-dep:webdriver AI (phantom-deps): webdriver is a declared runtime dep used via spec-driver-webdriver; phantom-dep heuristic false positive. ai

Versions (showing 18 of 18)

Version Deps Published
1.0.17 11 / 7
1.0.16 11 / 7
1.0.15 11 / 7
1.0.14 11 / 6
1.0.13 11 / 6
1.0.12 11 / 6
1.0.11 11 / 6
1.0.10 11 / 6
1.0.9 11 / 6
1.0.8 11 / 6
1.0.7 11 / 6
1.0.6 11 / 6
1.0.5 11 / 6
1.0.4 11 / 6
1.0.3 11 / 6
1.0.2 11 / 6
1.0.1 11 / 6
1.0.0 11 / 6

v1.0.17

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.16

2 findings
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Publisher changed: danielputerman → movsho (on 2026-05-26, known maintainer) provenance

This version was published by a different npm account (movsho) than the most recent previously approved version (danielputerman) on 2026-05-26, but movsho 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.0.15

2 findings
HIGH Publisher changed: danielputerman → movsho (on 2026-05-19) provenance

This 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.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.14

2 findings
HIGH Publisher changed: danielputerman → movsho (on 2026-05-05) provenance

This version was published by a different npm account than previous versions on 2026-05-05. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.13

2 findings
HIGH Publisher changed: danielputerman → movsho (on 2026-05-04) provenance

This version was published by a different npm account than previous versions on 2026-05-04. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.12

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.11

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.10

1 finding
LOW No provenance attestation provenance

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
LOW No provenance attestation provenance

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
LOW No provenance attestation provenance

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
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.0.6

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.5

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.4

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.3

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.2

1 finding
LOW No provenance attestation provenance

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
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.