Is @types/signal-exit safe to use?

@types/signal-exit has no known vulnerabilities on the latest version (4.0.0). DepScope rates its health at 24/100 (critical risk).

What is the latest version of @types/signal-exit?

The latest version of @types/signal-exit is 4.0.0, released 2025-03-27.

Does @types/signal-exit have known vulnerabilities?

No known vulnerabilities on the latest version of @types/signal-exit.

Is @types/signal-exit deprecated?

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

What are alternatives to @types/signal-exit?

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

What license does @types/signal-exit use?

@types/signal-exit is licensed under MIT.

@types/signal-exit

npmv4.0.0deprecated

Stub TypeScript definitions entry for signal-exit, which provides its own types definitions

License MITpermissive6 versions1 maintainers1 deps27,710 weekly dl

/ 100

Health

find alternative

@types/signal-exit is deprecated — find an alternative

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

Health breakdown0 – 100

5/25

maintenance

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

signal-exit

API access

Get this data programmatically — free, no authentication.

curl https://depscope.dev/api/check/npm/@types/signal-exit