@pnpm/plugin-commands-env 3.1.25

pnpm commands for managing Node.js

@pnpm/plugin-commands-env@3.1.25 was published on 2023-02-01. Its manifest declares 15 runtime dependencies and 0 peer requirements. Type declarations are bundled according to the package metadata. The declared Node.js requirement is >=14.6.

All @pnpm/plugin-commands-env versions · Permanent reference to 3.1.25 · Latest release

Package specifications

Version3.1.25
License declarationMIT
Published2023-02-01T01:42:41.947Z
Node.js requirement>=14.6
Type declarationsBundled declarations
Runtime dependency count15
Peer requirement count0
Optional dependency count0
Minified sizeMeasurement not available yet
Minified + gzipMeasurement not available yet
Unpacked distribution size37.55 KiB
Published file count30
Package typeNot declared
ES module entryNot declared
Default entrylib/index.js
Side effects declarationNot declared
Direct advisories0
Resolved graph dependenciesUnknown
Repository stars36957
Repository forks1962

Install @pnpm/plugin-commands-env 3.1.25

npm install @pnpm/plugin-commands-env@3.1.25
pnpm add @pnpm/plugin-commands-env@3.1.25
yarn add @pnpm/plugin-commands-env@3.1.25

Runtime dependencies

Peer requirements

  • None declared

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.

Code-Review9/10 — Found 27/30 approved changesets -- score normalized to 9
Maintained10/10 — 30 commit(s) and 20 issue activity found in the last 90 days -- score normalized to 10
Security-Policy10/10 — security policy file detected
CII-Best-Practices0/10 — no effort to earn an OpenSSF best practices badge detected
Dangerous-Workflow10/10 — no dangerous workflow patterns detected
Token-Permissions0/10 — detected GitHub workflow tokens with excessive permissions
License10/10 — license file detected
Binary-Artifacts10/10 — no binaries found in the repo
Branch-Protection5/10 — branch protection is not maximal on development and all release branches
Pinned-Dependencies9/10 — dependency not pinned by hash detected -- score normalized to 9
Signed-Releases0/10 — Project has not signed or included provenance with any releases.
Packaging10/10 — packaging workflow detected
Fuzzing0/10 — project is not fuzzed
SAST10/10 — SAST tool is run on all commits

Evidence and freshness