← Home

@applitools/spec-driver-webdriver

npm Repository Homepage
21
Versions
—
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

Keywords

webdriverchrome devtools protocolcdpdevtoolswebdriverwebdriverjsapplitoolsautomationtestingtests

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
npm-metadata no-description AI (npm-metadata): Applitools monorepo package; missing description is a consistent pattern, not a malice indicator. ai
provenance no-provenance AI (provenance): Established Applitools SDK; no provenance is consistent across their entire package family. ai

Versions (showing 21 of 21)

Version Deps Published
1.6.2 4 / 7
1.6.1 4 / 7
1.6.0 4 / 6
1.5.10 4 / 6
1.5.9 4 / 6
1.5.8 4 / 6
1.5.7 4 / 6
1.5.6 4 / 6
1.5.5 4 / 6
1.5.3 4 / 6
1.5.2 4 / 6
1.5.0 4 / 6
1.4.5 4 / 6
1.4.4 4 / 6
1.4.3 4 / 6
1.4.2 4 / 6
1.4.1 4 / 6
1.4.0 4 / 6
1.3.1 4 / 6
1.3.0 4 / 6
1.2.6 4 / 6

v1.6.2

1 finding
INFO No provenance attestation provenance

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

v1.6.1

1 finding
INFO No provenance attestation provenance

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

v1.6.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.

v1.5.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.5.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.5.8

1 finding
INFO No provenance attestation provenance

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

v1.5.7

1 finding
INFO No provenance attestation provenance

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

v1.5.6

1 finding
INFO No provenance attestation provenance

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

v1.5.5

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

2 findings
HIGH Publisher changed: applitools-admin → danielputerman (on 2025-12-01) provenance

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

INFO No provenance attestation provenance

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

v1.5.2

2 findings
HIGH Publisher changed: applitools-admin → danielputerman (on 2025-11-20) provenance

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

INFO No provenance attestation provenance

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

v1.5.0

1 finding
LOW No provenance attestation provenance

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

v1.4.5

1 finding
LOW No provenance attestation provenance

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

v1.4.4

1 finding
LOW No provenance attestation provenance

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

v1.4.3

1 finding
LOW No provenance attestation provenance

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

v1.4.2

1 finding
LOW No provenance attestation provenance

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

v1.4.1

1 finding
LOW No provenance attestation provenance

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

v1.4.0

1 finding
LOW No provenance attestation provenance

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

v1.3.1

1 finding
LOW No provenance attestation provenance

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

v1.3.0

1 finding
LOW No provenance attestation provenance

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

v1.2.6

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.