signal-exit 4.0.1

when you want to fire an event no matter how a process exits.

signal-exit@4.0.1 was published on 2023-04-16. Its manifest declares 0 runtime dependencies and 0 peer requirements. Type declarations are bundled according to the package metadata. The declared Node.js requirement is >=14.

All signal-exit versions · Permanent reference to 4.0.1 · Latest release

Package specifications

Version4.0.1
License declarationISC
Published2023-04-16T06:14:51.490Z
Node.js requirement>=14
Type declarationsBundled declarations
Runtime dependency count0
Peer requirement count0
Optional dependency count0
Minified sizeMeasurement not available yet
Minified + gzipMeasurement not available yet
Unpacked distribution size70.62 KiB
Published file count29
Package typeNot declared
ES module entry./dist/mjs/index.js
Default entry./dist/cjs/index.js
Side effects declarationNot declared
Direct advisories0
Resolved graph dependencies0
Repository stars201
Repository forks27

Install signal-exit 4.0.1

npm install signal-exit@4.0.1
pnpm add signal-exit@4.0.1
yarn add signal-exit@4.0.1

Runtime dependencies

  • None declared

Peer requirements

  • None declared

Optional dependencies

  • None declared

Resolved dependency graph

This deps.dev graph describes a generic 64-bit Linux environment, not your application lockfile.

    How to interpret the specifications

    Bundlephobia measurements use its standard package build and may exclude peer dependencies. Unpacked npm distribution size includes shipped files and is a different measurement. Module declarations do not prove tree-shaking or runtime compatibility.

    Advisories apply to this package version directly; transitive dependencies need separate inspection. Repository signals describe the whole repository and are current observations, including on historical-version pages.

    OpenSSF repository checks

    Provider assessment: 2026-08-24T00:00:00Z. These are repository checks, not a jsL maintenance score.

    Dangerous-Workflow10/10 — no dangerous workflow patterns detected
    Maintained0/10 — 0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
    Code-Review0/10 — Found 0/30 approved changesets -- score normalized to 0
    Binary-Artifacts10/10 — no binaries found in the repo
    Token-Permissions0/10 — detected GitHub workflow tokens with excessive permissions
    Pinned-Dependencies0/10 — dependency not pinned by hash detected -- score normalized to 0
    CII-Best-Practices0/10 — no effort to earn an OpenSSF best practices badge detected
    Fuzzing0/10 — project is not fuzzed
    License10/10 — license file detected
    SAST0/10 — SAST tool is not run on all commits -- score normalized to 0
    Security-Policy10/10 — security policy file detected
    Branch-Protection0/10 — branch protection not enabled on development/release branches

    Evidence and freshness