catch-exit

Catch Node.js exit conditions, including errors and unhandled rejections.

catch-exit@2.0.0 was published on 2025-01-09. Its manifest declares 1 runtime dependency and 0 peer requirements. Type declarations are bundled according to the package metadata. The declared Node.js requirement is >=12.

All catch-exit versions · Permanent reference to 2.0.0

Package specifications

Version2.0.0
License declaration(MIT or CC0 1.0)
Published2025-01-09T14:37:31.637Z
Node.js requirement>=12
Type declarationsBundled declarations
Runtime dependency count1
Peer requirement count0
Optional dependency count0
Minified sizeMeasurement not available yet
Minified + gzipMeasurement not available yet
Unpacked distribution size20.15 KiB
Published file count6
Package typemodule
ES module entrydist/index.js
Default entrydist/index.js
Side effects declarationNot declared
Direct advisories0
Resolved graph dependencies1
Repository stars12
Repository forks1

Install catch-exit 2.0.0

npm install catch-exit@2.0.0
pnpm add catch-exit@2.0.0
yarn add catch-exit@2.0.0

Runtime dependencies

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.

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

Evidence and freshness