forever 4.0.1
A simple CLI tool for ensuring that a given node script runs continuously (i.e. forever)
forever@4.0.1 was published on 2021-06-12. Its manifest declares 14 runtime dependencies and 0 peer requirements. Bundled type declarations are not declared in the inspected metadata. The declared Node.js requirement is >=6.
All forever versions · Permanent reference to 4.0.1 · Latest release
Package specifications
| Version | 4.0.1 |
|---|---|
| License declaration | MIT |
| Published | 2021-06-12T12:03:52.680Z |
| Node.js requirement | >=6 |
| Type declarations | Not declared |
| Runtime dependency count | 14 |
| Peer requirement count | 0 |
| Optional dependency count | 0 |
| Minified size | Measurement not available yet |
| Minified + gzip | Measurement not available yet |
| Unpacked distribution size | 145.96 KiB |
| Published file count | 11 |
| Package type | Not declared |
| ES module entry | Not declared |
| Default entry | ./lib/forever |
| Side effects declaration | Not declared |
| Direct advisories | Unknown |
| Resolved graph dependencies | Unknown |
| Repository stars | 13814 |
| Repository forks | 931 |
Install forever 4.0.1
npm install forever@4.0.1 pnpm add forever@4.0.1 yarn add forever@4.0.1
Runtime dependencies
- async ^1.5.2
- cliff ^0.1.10
- clone ^2.1.2
- shush ^1.0.0
- colors ^0.6.2
- mkdirp ^0.5.5
- winston ~0.8.1
- flatiron ~0.4.3
- nssocket ^0.6.0
- prettyjson ^1.2.1
- configstore 4.0.0
- eventemitter2 6.4.4
- object-assign ^4.1.1
- forever-monitor ^3.0.3
Peer requirements
- None declared
Optional dependencies
- None declared
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.
| Code-Review | 3/10 — Found 10/30 approved changesets -- score normalized to 3 |
|---|---|
| Maintained | 0/10 — 0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0 |
| Binary-Artifacts | 10/10 — no binaries found in the repo |
| 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 |
| Branch-Protection | 0/10 — branch protection not enabled on development/release branches |
| SAST | 0/10 — SAST tool is not run on all commits -- score normalized to 0 |
Evidence and freshness
- https://registry.npmjs.org/forever/4.0.1 — retrieved 2026-10-31T19:00:22.430Z
- https://api.deps.dev/v3/projects/github.com%2Fforeverjs%2Fforever — retrieved 2026-10-31T16:26:58.056Z