terminate 2.7.0
Terminate a Node.js Process based on the Process ID
terminate@2.7.0 was published on 2024-07-01. 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 terminate versions · Permanent reference to 2.7.0 · Latest release
Package specifications
| Version | 2.7.0 |
|---|---|
| License declaration | GPL-2.0 |
| Published | 2024-07-01T08:28:22.053Z |
| Node.js requirement | >=12 |
| Type declarations | Bundled declarations |
| Runtime dependency count | 1 |
| Peer requirement count | 0 |
| Optional dependency count | 0 |
| Minified size | Measurement not available yet |
| Minified + gzip | Measurement not available yet |
| Unpacked distribution size | 44.37 KiB |
| Published file count | 11 |
| Package type | Not declared |
| ES module entry | Not declared |
| Default entry | terminate.js |
| Side effects declaration | Not declared |
| Direct advisories | 0 |
| Resolved graph dependencies | 9 |
| Repository stars | 79 |
| Repository forks | 15 |
Install terminate 2.7.0
npm install terminate@2.7.0 pnpm add terminate@2.7.0 yarn add terminate@2.7.0
Runtime dependencies
- ps-tree ^1.2.0
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.
- duplexer@0.1.2 — indirect
- event-stream@3.3.4 — indirect
- from@0.1.7 — indirect
- map-stream@0.1.0 — indirect
- pause-stream@0.0.11 — indirect
- ps-tree@1.2.0 — direct
- split@0.3.3 — indirect
- stream-combiner@0.0.4 — indirect
- through@2.3.8 — indirect
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-Workflow | 10/10 — no dangerous workflow patterns detected |
|---|---|
| Code-Review | 6/10 — Found 2/3 approved changesets -- score normalized to 6 |
| Maintained | 5/10 — 6 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 5 |
| Binary-Artifacts | 10/10 — no binaries found in the repo |
| Token-Permissions | 0/10 — detected GitHub workflow tokens with excessive permissions |
| Pinned-Dependencies | 4/10 — dependency not pinned by hash detected -- score normalized to 4 |
| CII-Best-Practices | 0/10 — no effort to earn an OpenSSF best practices badge detected |
| Security-Policy | 0/10 — security policy file not detected |
| Fuzzing | 0/10 — project is not fuzzed |
| License | 10/10 — license file detected |
| SAST | 0/10 — SAST tool is not run on all commits -- score normalized to 0 |
Evidence and freshness
- https://registry.npmjs.org/terminate/2.7.0 — retrieved 2026-10-29T15:10:23.572Z
- https://api.deps.dev/v3/projects/github.com%2Fdwyl%2Fterminate — retrieved 2026-10-29T12:51:36.205Z
- https://api.deps.dev/v3/systems/npm/packages/terminate/versions/2.7.0 — retrieved 2026-10-29T15:10:24.090Z
- https://api.deps.dev/v3/systems/npm/packages/terminate/versions/2.7.0:dependencies — retrieved 2026-10-29T15:10:24.093Z