Is @pnpm/config.version-policy safe to use?

@pnpm/config.version-policy has no known vulnerabilities on the latest version (1100.0.1). DepScope rates its health at 67/100 (moderate risk).

What is the latest version of @pnpm/config.version-policy?

The latest version of @pnpm/config.version-policy is 1100.0.1, released 2026-04-15.

No known vulnerabilities on the latest version of @pnpm/config.version-policy.

No, @pnpm/config.version-policy is actively maintained. Latest release: 1100.0.1 (2026-04-15).

Popular alternatives to @pnpm/config.version-policy in npm include: minimatch, commander, eslint-visitor-keys, ajv, color-name.

@pnpm/config.version-policy is licensed under MIT.

npmv1100.0.1

Parses and evaluates package version policy specs and produces package-version matchers

License MITpermissive9 versions2 maintainers4 deps

/ 100

Health

safe to use

@pnpm/[email protected] is safe to use (health: 67/100)

Health breakdown0 – 100

25/25

maintenance

0/20

popularity

25/25

security

6/15

maturity

11/15

community

Vulnerabilities

none known

🌟

10/10typed

bundled

Dependencies (4)

API access

Get this data programmatically — free, no authentication.

curl https://depscope.dev/api/check/npm/@pnpm/config.version-policy