Is @pnpm/parse-wanted-dependency safe to use?

@pnpm/parse-wanted-dependency has no known vulnerabilities on the latest version (1001.0.0). DepScope rates its health at 59/100 (high risk).

What is the latest version of @pnpm/parse-wanted-dependency?

The latest version of @pnpm/parse-wanted-dependency is 1001.0.0, released 2025-04-21.

Does @pnpm/parse-wanted-dependency have known vulnerabilities?

No known vulnerabilities on the latest version of @pnpm/parse-wanted-dependency.

Is @pnpm/parse-wanted-dependency deprecated?

No, @pnpm/parse-wanted-dependency is actively maintained. Latest release: 1001.0.0 (2025-04-21).

What are alternatives to @pnpm/parse-wanted-dependency?

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

What license does @pnpm/parse-wanted-dependency use?

@pnpm/parse-wanted-dependency is licensed under MIT.

@pnpm/parse-wanted-dependency

npmv1001.0.0

Parse dependency specifier

License MITpermissive13 versions2 maintainers1 deps360,181 weekly dl

pnpm/pnpm/blob/main/packages/parse-wanted-dependency

/ 100

Health

safe to use

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

Health breakdown0 – 100

5/25

maintenance

14/20

popularity

25/25

security

12/15

maturity

3/15

community

Vulnerabilities

none known

Bundle & TypeScript

🌟

TypeScript

10/10typed

bundled

Health History

Dependency Tree

License Audit

Dependencies (1)

validate-npm-package-name

API access

Get this data programmatically — free, no authentication.

curl https://depscope.dev/api/check/npm/@pnpm/parse-wanted-dependency