Is @pnpm/lockfile-to-pnp safe to use?

@pnpm/lockfile-to-pnp has no known vulnerabilities on the latest version (1001.0.34). DepScope rates its health at 63/100 (moderate risk).

What is the latest version of @pnpm/lockfile-to-pnp?

The latest version of @pnpm/lockfile-to-pnp is 1001.0.34, released 2026-03-24.

Does @pnpm/lockfile-to-pnp have known vulnerabilities?

No known vulnerabilities on the latest version of @pnpm/lockfile-to-pnp.

Is @pnpm/lockfile-to-pnp deprecated?

No, @pnpm/lockfile-to-pnp is actively maintained. Latest release: 1001.0.34 (2026-03-24).

What are alternatives to @pnpm/lockfile-to-pnp?

Popular alternatives to @pnpm/lockfile-to-pnp in npm include: semver, minimatch, ansi-styles, debug, brace-expansion.

What license does @pnpm/lockfile-to-pnp use?

@pnpm/lockfile-to-pnp is licensed under MIT.

@pnpm/lockfile-to-pnp

npmv1001.0.34

Creates a Plug'n'Play file from a pnpm-lock.yaml

License MITpermissive223 versions2 maintainers7 deps

pnpm/pnpm.git#main

/ 100

Health

safe to use

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

Health breakdown0 – 100

20/25

maintenance

0/20

popularity

25/25

security

15/15

maturity

3/15

community

Vulnerabilities

none known

Bundle & TypeScript

🌟

TypeScript

10/10typed

bundled

Health History

Dependency Tree

License Audit

Dependencies (7)

@yarnpkg/pnp normalize-path ramda @pnpm/dependency-path @pnpm/lockfile.fs @pnpm/lockfile.utils @pnpm/types

API access

Get this data programmatically — free, no authentication.

curl https://depscope.dev/api/check/npm/@pnpm/lockfile-to-pnp