Is @types/read-pkg safe to use?

@types/read-pkg has no known vulnerabilities on the latest version (5.1.0). DepScope rates its health at 36/100 (critical risk).

What is the latest version of @types/read-pkg?

The latest version of @types/read-pkg is 5.1.0, released 2019-07-17.

Does @types/read-pkg have known vulnerabilities?

No known vulnerabilities on the latest version of @types/read-pkg.

Is @types/read-pkg deprecated?

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

What are alternatives to @types/read-pkg?

Popular alternatives to @types/read-pkg in npm include: ?, semver, minimatch, debug, brace-expansion.

What license does @types/read-pkg use?

@types/read-pkg is licensed under MIT.

@types/read-pkg

npmv5.1.0deprecated

Stub TypeScript definitions entry for read-pkg, which provides its own types definitions

License MITpermissive3 versions1 maintainers1 deps48,757 weekly dl

sindresorhus/read-pkg

/ 100

Health

find alternative

@types/read-pkg is deprecated — find an alternative

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

Health breakdown0 – 100

15/25

maintenance

10/20

popularity

25/25

security

12/15

maturity

4/15

community

Vulnerabilities

none known

Bundle & TypeScript

🌟

TypeScript

0/10untyped

No type definitions available

Health History

Dependency Tree

License Audit

Dependencies (1)

read-pkg

API access

Get this data programmatically — free, no authentication.

curl https://depscope.dev/api/check/npm/@types/read-pkg