blocking-proxy 0.0.2

WebDriver Proxy for testing rich clients. It block certain calls until Angular is done updating the page under test.

blocking-proxy@0.0.2 was published on 2016-12-14. Its manifest declares 3 runtime dependencies and 0 peer requirements. Type declarations are bundled according to the package metadata. No Node.js engine requirement is declared in this manifest.

All blocking-proxy versions · Permanent reference to 0.0.2 · Latest release

Package specifications

Version0.0.2
License declarationMIT
Published2016-12-14T00:52:58.800Z
Node.js requirementNot declared
Type declarationsBundled declarations
Runtime dependency count3
Peer requirement count0
Optional dependency count0
Minified sizeMeasurement not available yet
Minified + gzipMeasurement not available yet
Unpacked distribution sizeNot supplied
Published file countNot supplied
Package typeNot declared
ES module entryNot declared
Default entrybuilt/lib/index.js
Side effects declarationNot declared
Direct advisories0
Resolved graph dependencies23
Repository stars46
Repository forks36

Install blocking-proxy 0.0.2

npm install blocking-proxy@0.0.2
pnpm add blocking-proxy@0.0.2
yarn add blocking-proxy@0.0.2

Runtime dependencies

Peer requirements

  • None declared

Optional dependencies

  • None declared

Resolved dependency graph

This deps.dev graph describes a generic 64-bit Linux environment, not your application lockfile.

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.

Binary-Artifacts10/10 — no binaries found in the repo
Code-Review3/10 — Found 9/30 approved changesets -- score normalized to 3
Maintained0/10 — project is archived
CII-Best-Practices0/10 — no effort to earn an OpenSSF best practices badge detected
Fuzzing0/10 — project is not fuzzed
License10/10 — license file detected
Security-Policy10/10 — security policy file detected
Branch-Protection3/10 — branch protection is not maximal on development and all release branches
SAST0/10 — SAST tool is not run on all commits -- score normalized to 0

Evidence and freshness