create-wdio
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 |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): WebdriverIO monorepo migrated to GitHub Actions publishing with SLSA attestation; stable for this package. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Dormancy reflects monorepo CI migration, not account takeover; SLSA provenance confirms legitimate publish. | ai |
Versions (showing 10 of 10)
| Version | Deps | Published |
|---|---|---|
| 9.27.1 | 13 / 6 | |
| 9.27.0 | 13 / 6 | |
| 9.26.1 | 13 / 6 | |
| 9.26.0 | 13 / 6 | |
| 9.25.0 | 13 / 6 | |
| 9.21.0 | 13 / 6 | |
| 9.18.2 | 13 / 6 | |
| 9.18.0 | 13 / 6 | |
| 9.17.1 | 13 / 6 | |
| 9.17.0 | 13 / 6 |
v9.27.1
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.1
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
2 findingsThis version was published by a different npm account than previous versions on 2026-03-10. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v9.21.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v9.18.2
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.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.17.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.