chromium-bidi
An implementation of the WebDriver BiDi protocol for Chromium implemented as a JavaScript layer translating between BiDi and CDP, running inside a Chrome tab.
Supply chain provenance
Status for the latest visible version.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Google's chromium-bidi migrated from google-wombot bot account to GitHub Actions OIDC publishing — a standard, expected transition for Google OSS packages. SLSA provenance attestation confirms legitimate CI/CD origin. | ai | |
| semgrep | semgrep:base64-decode | AI (semgrep): Base64 decode is a legitimate utility in a WebDriver BiDi implementation for encoding/decoding protocol data. The code is transparent and non-obfuscated. | ai | |
| phantom-deps | phantom-dep:puppeteer | AI (phantom-deps): puppeteer is a runtime dep in package.json; phantom-dep fires because it's not directly imported in source, consistent with config-level integration in this Chrome automation library. | ai |
Versions (showing 100 of 137)
| Version | Deps | Published |
|---|---|---|
| 16.0.1 | 2 / 44 | |
| 15.0.0 | 2 / 44 | |
| 14.0.0 | 2 / 44 | |
| 13.1.1 | 2 / 44 | |
| 13.1.0 | 3 / 44 | |
| 13.0.1 | 2 / 44 | |
| 13.0.0 | 2 / 44 | |
| 12.1.0 | 2 / 44 | |
| 12.0.1 | 2 / 44 | |
| 12.0.0 | 2 / 44 | |
| 11.0.1 | 2 / 44 | |
| 11.0.0 | 2 / 45 | |
| 10.6.1 | 2 / 46 | |
| 10.6.0 | 2 / 46 | |
| 10.5.1 | 2 / 46 | |
| 10.5.0 | 2 / 46 | |
| 10.4.0 | 2 / 46 | |
| 10.3.1 | 2 / 46 | |
| 10.3.0 | 2 / 46 | |
| 10.2.0 | 2 / 46 | |
| 10.1.0 | 2 / 46 | |
| 10.0.0 | 2 / 46 | |
| 9.2.1 | 2 / 46 | |
| 9.2.0 | 2 / 46 | |
| 9.1.0 | 2 / 46 | |
| 9.0.0 | 2 / 46 | |
| 8.1.0 | 2 / 46 | |
| 8.0.0 | 2 / 46 | |
| 7.3.2 | 2 / 46 | |
| 7.3.1 | 2 / 46 | |
| 7.3.0 | 2 / 46 | |
| 7.2.0 | 2 / 46 | |
| 7.1.1 | 2 / 46 | |
| 7.1.0 | 2 / 46 | |
| 7.0.0 | 2 / 46 | |
| 6.1.0 | 2 / 46 | |
| 6.0.0 | 2 / 46 | |
| 5.3.1 | 2 / 46 | |
| 5.3.0 | 2 / 46 | |
| 5.2.0 | 2 / 46 | |
| 5.1.0 | 2 / 48 | |
| 5.0.0 | 2 / 48 | |
| 4.2.0 | 2 / 48 | |
| 4.1.1 | 2 / 48 | |
| 4.1.0 | 2 / 48 | |
| 4.0.1 | 2 / 48 | |
| 4.0.0 | 2 / 48 | |
| 3.2.1 | 2 / 48 | |
| 3.2.0 | 2 / 48 | |
| 3.1.0 | 2 / 48 | |
| 3.0.0 | 2 / 48 | |
| 2.1.2 | 2 / 48 | |
| 2.1.1 | 2 / 48 | |
| 2.1.0 | 2 / 48 | |
| 2.0.0 | 2 / 47 | |
| 1.3.0 | 2 / 47 | |
| 1.2.0 | 2 / 47 | |
| 1.1.0 | 2 / 47 | |
| 1.0.0 | 2 / 47 | |
| 0.12.0 | 2 / 47 | |
| 0.11.1 | 2 / 48 | |
| 0.11.0 | 2 / 48 | |
| 0.10.2 | 2 / 48 | |
| 0.10.1 | 3 / 49 | |
| 0.10.0 | 3 / 49 | |
| 0.9.1 | 3 / 49 | |
| 0.9.0 | 3 / 49 | |
| 0.8.1 | 3 / 49 | |
| 0.8.0 | 3 / 49 | |
| 0.7.1 | 3 / 49 | |
| 0.7.0 | 3 / 50 | |
| 0.6.5 | 3 / 49 | |
| 0.6.4 | 3 / 44 | |
| 0.6.3 | 3 / 44 | |
| 0.6.2 | 3 / 44 | |
| 0.6.1 | 3 / 44 | |
| 0.6.0 | 3 / 44 | |
| 0.5.24 | 3 / 44 | |
| 0.5.23 | 3 / 45 | |
| 0.5.22 | 3 / 45 | |
| 0.5.21 | 3 / 45 | |
| 0.5.20 | 3 / 45 | |
| 0.5.19 | 3 / 45 | |
| 0.5.18 | 3 / 45 | |
| 0.5.17 | 3 / 45 | |
| 0.5.16 | 3 / 45 | |
| 0.5.15 | 3 / 45 | |
| 0.5.14 | 3 / 45 | |
| 0.5.13 | 3 / 47 | |
| 0.5.12 | 2 / 50 | |
| 0.5.11 | 2 / 50 | |
| 0.5.10 | 2 / 49 | |
| 0.5.9 | 2 / 49 | |
| 0.5.8 | 2 / 49 | |
| 0.5.7 | 2 / 49 | |
| 0.5.6 | 2 / 49 | |
| 0.5.5 | 2 / 49 | |
| 0.5.4 | 2 / 48 | |
| 0.5.3 | 2 / 47 | |
| 0.5.2 | 2 / 48 |
v16.0.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v15.0.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v14.0.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v13.1.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v13.1.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v13.0.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v13.0.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v12.1.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v12.0.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v12.0.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v11.0.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v11.0.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v10.6.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v10.6.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v10.5.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v10.5.0
2 findingsThis version was published by a different npm account than previous versions on 2025-10-17. 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.
v10.4.0
2 findingsThis version was published by a different npm account than previous versions on 2025-10-15. 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.
v10.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.3.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.12.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.24
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.23
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.22
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.21
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.20
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.