@applitools/eyes-webdriverio SEE LICENSE IN LICENSE 46 versions

@applitools/eyes-webdriverio

npm Homepage

Applitools Eyes SDK for WebdriverIO

46

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

Keywords

eyes-webdriverioapplitoolseyestest automationvisual regressionautomationtestingtestswebdriverio

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): Established Applitools org package with 290 versions; dormancy likely reflects release cadence, not takeover.	ai	2026/05/15
dependencies	unvetted-dep:@applitools/driver	AI (dependencies): Internal @applitools scoped dep; consistent with this SDK's established dependency pattern.	ai	2026/04/30
dependencies	unvetted-dep:@applitools/spec-driver-webdriver	AI (dependencies): Internal @applitools scoped dep; consistent with this SDK's established dependency pattern.	ai	2026/04/30
phantom-deps	phantom-dep:@applitools/driver	AI (phantom-deps): Same-org transitive dep; phantom-dep heuristic is a stable false positive for this monorepo package.	ai	2026/04/29

Versions (showing 46 of 46)

Version	Deps	Published
5.60.3	3 / 15	2026-06-04
5.60.2	3 / 15	2026-05-26
5.60.1	3 / 15	2026-05-19
5.59.39	3 / 13	2026-04-29
5.59.38	3 / 13	2026-04-27
5.59.37	3 / 13	2026-04-19
5.59.36	3 / 13	2026-04-13
5.59.35	3 / 13	2026-04-07
5.59.34	3 / 13	2026-03-29
5.59.33	3 / 13	2026-03-16
5.59.32	3 / 13	2026-03-16
5.59.31	3 / 13	2026-03-12
5.59.30	3 / 13	2026-03-08
5.59.29	3 / 13	2026-03-08
5.59.28	3 / 13	2026-03-03
5.59.27	3 / 13	2026-03-02
5.59.26	3 / 13	2026-02-24
5.59.25	3 / 13	2026-02-16
5.59.24	3 / 13	2026-01-28
5.59.23	3 / 13	2026-01-22
5.59.22	3 / 13	2026-01-20
5.59.21	3 / 13	2026-01-14
5.59.20	3 / 13	2026-01-11
5.59.19	3 / 13	2025-12-28
5.59.18	3 / 13	2025-12-15
5.59.17	3 / 13	2025-12-07
5.59.16	3 / 13	2025-11-20
5.59.15	3 / 13	2025-11-10
5.59.14	3 / 13	2025-11-03
5.59.13	3 / 13	2025-10-23
5.59.12	3 / 13	2025-10-22
5.59.11	3 / 13	2025-10-16
5.59.10	3 / 13	2025-10-09
5.59.9	3 / 13	2025-10-01
5.59.8	3 / 13	2025-09-22
5.59.7	3 / 13	2025-09-16
5.59.6	3 / 13	2025-09-15
5.59.5	3 / 13	2025-09-09
5.59.4	3 / 13	2025-09-05
5.59.3	3 / 13	2025-08-27
5.59.2	3 / 13	2025-08-21
5.59.1	3 / 13	2025-08-13
5.59.0	3 / 13	2025-08-05
5.58.5	3 / 13	2025-07-23
5.58.4	3 / 13	2025-07-15
5.58.3	3 / 13	2025-06-16

v5.60.3

1 finding

LOW No provenance attestation provenance

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

v5.60.2

1 finding

LOW No provenance attestation provenance

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

v5.60.1

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-19, known maintainer) provenance

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

v5.59.39

1 finding

LOW No provenance attestation provenance

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

v5.59.37

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.

v5.59.36

1 finding

LOW No provenance attestation provenance

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

v5.59.35

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.

v5.59.34

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.

v5.59.33

1 finding

LOW No provenance attestation provenance

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

v5.59.32

1 finding

LOW No provenance attestation provenance

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

v5.59.31

1 finding

LOW No provenance attestation provenance

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

v5.59.30

1 finding

LOW No provenance attestation provenance

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

v5.59.29

1 finding

LOW No provenance attestation provenance

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

v5.59.28

1 finding

LOW No provenance attestation provenance

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

v5.59.27

1 finding

LOW No provenance attestation provenance

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

v5.59.26

1 finding

LOW No provenance attestation provenance

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

v5.59.25

1 finding

LOW No provenance attestation provenance

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

v5.59.24

1 finding

LOW No provenance attestation provenance

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

v5.59.23

1 finding

LOW No provenance attestation provenance

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

v5.59.22

1 finding

LOW No provenance attestation provenance

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

v5.59.21

1 finding

LOW No provenance attestation provenance

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

v5.59.20

1 finding

LOW No provenance attestation provenance

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

v5.59.19

1 finding

LOW No provenance attestation provenance

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

v5.59.18

1 finding

LOW No provenance attestation provenance

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

v5.59.17

1 finding

LOW No provenance attestation provenance

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

v5.59.16

1 finding

LOW No provenance attestation provenance

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

v5.59.15

1 finding

LOW No provenance attestation provenance

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

v5.59.14

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.

v5.59.13

1 finding

LOW No provenance attestation provenance

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

v5.59.12

1 finding

LOW No provenance attestation provenance

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

v5.59.11

1 finding

LOW No provenance attestation provenance

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

v5.59.10

1 finding

LOW No provenance attestation provenance

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

v5.59.9

1 finding

LOW No provenance attestation provenance

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

v5.59.8

1 finding

LOW No provenance attestation provenance

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

v5.59.7

1 finding

LOW No provenance attestation provenance

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

v5.59.6

1 finding

LOW No provenance attestation provenance

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

v5.59.5

1 finding

LOW No provenance attestation provenance

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

v5.59.4

1 finding

LOW No provenance attestation provenance

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

v5.59.3

1 finding

LOW No provenance attestation provenance

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

v5.59.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.

v5.59.1

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.

v5.59.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.

v5.58.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.

v5.58.4

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.

v5.58.3

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.