@percy/client 1.32.8-beta.4

Communicate with Percy's API to create builds and snapshots, upload resources, and finalize builds and snapshots. Uses [`@percy/env`](.packages/env) to send environment information with new builds. Can also be used to query for a project's builds using a

@percy/client@1.32.8-beta.4 was published on 2026-08-31. Its manifest declares 5 runtime dependencies and 0 peer requirements. Bundled type declarations are not declared in the inspected metadata. The declared Node.js requirement is >=14.

All @percy/client versions · Permanent reference to 1.32.8-beta.4 · Latest release

Package specifications

Version1.32.8-beta.4
License declarationMIT
Published2026-08-31T08:14:01.355Z
Node.js requirement>=14
Type declarationsNot declared
Runtime dependency count5
Peer requirement count0
Optional dependency count0
Minified sizeMeasurement not available yet
Minified + gzipMeasurement not available yet
Unpacked distribution size75.31 KiB
Published file count9
Package typemodule
ES module entryNot declared
Default entry./dist/index.js
Side effects declarationNot declared
Direct advisories0
Resolved graph dependencies51
Repository stars87
Repository forks60

Install @percy/client 1.32.8-beta.4

npm install @percy/client@1.32.8-beta.4
pnpm add @percy/client@1.32.8-beta.4
yarn add @percy/client@1.32.8-beta.4

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 0 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
Dangerous-Workflow10/10 — no dangerous workflow patterns detected
Binary-Artifacts10/10 — no binaries found in the repo
Token-Permissions0/10 — detected GitHub workflow tokens with excessive permissions
Pinned-Dependencies9/10 — dependency not pinned by hash detected -- score normalized to 9
Security-Policy0/10 — security policy file not detected
License0/10 — license file not detected
Signed-Releases0/10 — Project has not signed or included provenance with any releases.
Fuzzing0/10 — project is not fuzzed
SAST4/10 — SAST tool is not run on all commits -- score normalized to 4

Evidence and freshness