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.

chromium-bidi@159.0.8130-0 was published on 2026-10-29. Its manifest declares 2 runtime dependencies and 1 peer requirement. Type declarations are bundled according to the package metadata. The declared Node.js requirement is >=20.19.0 <22.0.0 || >=22.12.0.

All chromium-bidi versions · Permanent reference to 159.0.8130-0

Package specifications

Version159.0.8130-0
License declarationApache-2.0
Published2026-10-29T04:51:44.670Z
Node.js requirement>=20.19.0 <22.0.0 || >=22.12.0
Type declarationsBundled declarations
Runtime dependency count2
Peer requirement count1
Optional dependency count0
Minified sizeMeasurement not available yet
Minified + gzipMeasurement not available yet
Unpacked distribution size9385.57 KiB
Published file count319
Package typemodule
ES module entryNot declared
Default entry./out/Default/gen/src/index.js
Side effects declarationNot declared
Direct advisories0
Resolved graph dependenciesUnknown
Repository stars173
Repository forks55

Install chromium-bidi 159.0.8130-0

npm install chromium-bidi@159.0.8130-0
pnpm add chromium-bidi@159.0.8130-0
yarn add chromium-bidi@159.0.8130-0

Runtime dependencies

Peer requirements

Optional dependencies

  • None declared

How to interpret the specifications

Bundlephobia measurements use its standard package build and may exclude peer dependencies. Unpacked npm distribution size includes shipped files and is a different measurement. Module declarations do not prove tree-shaking or runtime compatibility.

Advisories apply to this package version directly; transitive dependencies need separate inspection. Repository signals describe the whole repository and are current observations, including on historical-version pages.

OpenSSF repository checks

Provider assessment: 2026-08-24T00:00:00Z. These are repository checks, not a jsL maintenance score.

Maintained10/10 — 30 commit(s) and 8 issue activity found in the last 90 days -- score normalized to 10
Security-Policy10/10 — security policy file detected
Code-Review10/10 — all changesets reviewed
Dangerous-Workflow10/10 — no dangerous workflow patterns detected
CII-Best-Practices0/10 — no effort to earn an OpenSSF best practices badge detected
Token-Permissions9/10 — detected GitHub workflow tokens with excessive permissions
Binary-Artifacts10/10 — no binaries found in the repo
Pinned-Dependencies6/10 — dependency not pinned by hash detected -- score normalized to 6
License10/10 — license file detected
Fuzzing0/10 — project is not fuzzed
Branch-Protection4/10 — branch protection is not maximal on development and all release branches
Packaging10/10 — packaging workflow detected
SAST4/10 — SAST tool is not run on all commits -- score normalized to 4

Evidence and freshness