@wdio/local-runner
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:stream-buffers | AI (dependencies): stream-buffers is a stable, well-known utility; no malicious history; stable dependency for this package. | ai | |
| phantom-deps | phantom-dep:@types/node | AI (phantom-deps): Type-only package; not imported at runtime, stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:expect-webdriverio | AI (phantom-deps): Referenced in config files by convention, not directly imported; stable false positive for this package. | ai |
Versions (showing 51 of 98)
| Version | Deps | Published |
|---|---|---|
| 9.30.0 | 10 / 1 | |
| 9.29.1 | 10 / 1 | |
| 9.29.0 | 10 / 1 | |
| 9.28.0 | 10 / 1 | |
| 9.27.2 | 10 / 1 | |
| 9.27.1 | 10 / 1 | |
| 9.27.0 | 10 / 1 | |
| 9.26.1 | 10 / 1 | |
| 9.26.0 | 10 / 1 | |
| 9.25.0 | 10 / 1 | |
| 9.24.0 | 10 / 1 | |
| 9.23.3 | 10 / 1 | |
| 9.23.2 | 10 / 1 | |
| 9.23.1 | 10 / 1 | |
| 9.23.0 | 10 / 1 | |
| 9.22.0 | 10 / 1 | |
| 9.21.0 | 10 / 1 | |
| 9.20.1 | 10 / 1 | |
| 9.20.0 | 10 / 1 | |
| 9.19.2 | 10 / 1 | |
| 9.19.1 | 10 / 1 | |
| 9.19.0 | 10 / 1 | |
| 9.18.4 | 9 / 1 | |
| 9.18.3 | 9 / 1 | |
| 9.18.1 | 9 / 1 | |
| 9.18.0 | 9 / 1 | |
| 9.17.0 | 9 / 1 | |
| 9.16.2 | 9 / 1 | |
| 9.16.1 | 9 / 1 | |
| 9.16.0 | 9 / 1 | |
| 9.15.0 | 8 / 2 | |
| 9.14.0 | 8 / 2 | |
| 9.13.0 | 8 / 2 | |
| 9.12.7 | 8 / 2 | |
| 9.12.6 | 8 / 2 | |
| 9.12.5 | 8 / 2 | |
| 9.12.4 | 8 / 2 | |
| 9.12.3 | 8 / 2 | |
| 9.12.2 | 8 / 2 | |
| 9.12.1 | 8 / 2 | |
| 9.12.0 | 8 / 2 | |
| 9.11.0 | 8 / 2 | |
| 9.10.1 | 8 / 2 | |
| 9.10.0 | 8 / 2 | |
| 9.9.3 | 8 / 2 | |
| 9.9.2 | 8 / 2 | |
| 9.9.1 | 8 / 2 | |
| 9.9.0 | 8 / 2 | |
| 9.8.0 | 8 / 2 | |
| 9.7.3 | 8 / 2 | |
| 9.7.2 | 8 / 2 |
v9.30.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v9.27.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v9.26.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v9.25.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v9.23.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v9.23.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v9.23.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v9.22.0
2 findingsPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
This version was published by a different npm account (GitHub Actions) than the most recent previously approved version (wdio-user) on 2025-12-24, but it carries Sigstore provenance attestation. This means the package moved to a trusted publisher (CI/CD with OIDC, e.g. GitHub Actions) — a supply-chain integrity improvement, not a compromise, since a stolen npm token cannot forge provenance bound to the source repository. Recorded as INFO for audit trail.
v9.20.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.20.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.19.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.19.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.19.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.18.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.18.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.18.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.18.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.17.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.16.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.16.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.16.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.15.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.14.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.12.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.12.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.12.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.12.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.12.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.12.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.12.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.12.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.11.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.10.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.10.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.9.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.9.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.9.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.9.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.7.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.7.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.