@percy/cli-command 1.32.13-beta.1

Percy CLI command parser and runner.

@percy/cli-command@1.32.13-beta.1 was published on 2026-10-29. 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/cli-command versions · Permanent reference to 1.32.13-beta.1 · Latest release

Package specifications

Version1.32.13-beta.1
License declarationMIT
Published2026-10-29T12:03:44.113Z
Node.js requirement>=14
Type declarationsNot declared
Runtime dependency count5
Peer requirement count0
Optional dependency count1
Minified sizeMeasurement not available yet
Minified + gzipMeasurement not available yet
Unpacked distribution size112.97 KiB
Published file count16
Package typemodule
ES module entryNot declared
Default entry./dist/index.js
Side effects declarationNot declared
Direct advisories0
Resolved graph dependenciesUnknown
Repository stars87
Repository forks60

Install @percy/cli-command 1.32.13-beta.1

npm install @percy/cli-command@1.32.13-beta.1
pnpm add @percy/cli-command@1.32.13-beta.1
yarn add @percy/cli-command@1.32.13-beta.1

Runtime dependencies

Peer requirements

  • None declared

Optional dependencies

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