Is @types/parse-package-name safe to use?

@types/parse-package-name has no known vulnerabilities on the latest version (1.0.0). DepScope rates its health at 33/100 (critical risk).

What is the latest version of @types/parse-package-name?

The latest version of @types/parse-package-name is 1.0.0, released 2025-05-31.

Does @types/parse-package-name have known vulnerabilities?

No known vulnerabilities on the latest version of @types/parse-package-name.

Is @types/parse-package-name deprecated?

Yes, @types/parse-package-name is deprecated: This is a stub types definition. parse-package-name provides its own type definitions, so you do not need this installed. Consider using semver instead.

What are alternatives to @types/parse-package-name?

Popular alternatives to @types/parse-package-name in npm include: semver, ansi-styles, minimatch, debug, brace-expansion.

What license does @types/parse-package-name use?

@types/parse-package-name is licensed under MIT.

@types/parse-package-name

npmv1.0.0deprecated

Stub TypeScript definitions entry for parse-package-name, which provides its own types definitions

License MITpermissive5 versions1 maintainers1 deps335,252 weekly dl

/ 100

Health

find alternative

@types/parse-package-name is deprecated — find an alternative

Moderate health score (33/100) — verify manually
Package is deprecated

Health breakdown0 – 100

10/25

maintenance

14/20

popularity

25/25

security

12/15

maturity

2/15

community

Vulnerabilities

none known

Bundle & TypeScript

🌟

TypeScript

0/10untyped

No type definitions available

Health History

Dependency Tree

License Audit

Dependencies (1)

parse-package-name

API access

Get this data programmatically — free, no authentication.

curl https://depscope.dev/api/check/npm/@types/parse-package-name