@playwright/test 0.162.0

A test runner for running tests with Playwright.

@playwright/test@0.162.0 was published on 2020-11-18. Its manifest declares 3 runtime dependencies and 0 peer requirements. Bundled type declarations are not declared in the inspected metadata. The declared Node.js requirement is >=10.17.0.

Deprecated: Please update to the latest version of Playwright to test up-to-date browsers.

All @playwright/test versions · Permanent reference to 0.162.0 · Latest release

Package specifications

Version0.162.0
License declarationApache-2.0
Published2020-11-18T22:31:12.800Z
Node.js requirement>=10.17.0
Type declarationsNot declared
Runtime dependency count3
Peer requirement count0
Optional dependency count0
Minified sizeMeasurement not available yet
Minified + gzipMeasurement not available yet
Unpacked distribution size35.77 KiB
Published file count5
Package typeNot declared
ES module entryNot declared
Default entryout/index.js
Side effects declarationNot declared
Direct advisories0
Resolved graph dependencies222
Repository stars98387
Repository forks6676

Install @playwright/test 0.162.0

npm install @playwright/test@0.162.0
pnpm add @playwright/test@0.162.0
yarn add @playwright/test@0.162.0

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.

Maintained10/10 — 30 commit(s) and 10 issue activity found in the last 90 days -- score normalized to 10
Code-Review10/10 — all changesets reviewed
CII-Best-Practices0/10 — no effort to earn an OpenSSF best practices badge detected
Security-Policy10/10 — security policy file detected
Dangerous-Workflow10/10 — no dangerous workflow patterns detected
License10/10 — license file detected
Token-Permissions0/10 — detected GitHub workflow tokens with excessive permissions
Binary-Artifacts7/10 — binaries present in source code
Pinned-Dependencies5/10 — dependency not pinned by hash detected -- score normalized to 5
SAST0/10 — SAST tool is not run on all commits -- score normalized to 0
Fuzzing0/10 — project is not fuzzed
Branch-Protection0/10 — branch protection not enabled on development/release branches

Evidence and freshness