Is @types/get-port safe to use?

@types/get-port has no known vulnerabilities on the latest version (4.2.0). DepScope rates its health at 45/100 (high risk).

What is the latest version of @types/get-port?

The latest version of @types/get-port is 4.2.0, released 2019-03-25.

Does @types/get-port have known vulnerabilities?

No known vulnerabilities on the latest version of @types/get-port.

Is @types/get-port deprecated?

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

What are alternatives to @types/get-port?

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

What license does @types/get-port use?

@types/get-port is licensed under MIT.

@types/get-port

npmv4.2.0deprecated

Stub TypeScript definitions entry for get-port, which provides its own types definitions

License MITpermissive8 versions1 maintainers1 deps377,132 weekly dl

sindresorhus/get-port

/ 100

Health

find alternative

@types/get-port is deprecated — find an alternative

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

Health breakdown0 – 100

20/25

maintenance

14/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)

get-port

API access

Get this data programmatically — free, no authentication.

curl https://depscope.dev/api/check/npm/@types/get-port