forever

A simple CLI tool for ensuring that a given node script runs continuously (i.e. forever)

forever@4.0.3 was published on 2022-01-28. 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.3

Package specifications

Version4.0.3
License declarationMIT
Published2022-01-28T20:23:35.467Z
Node.js requirement>=6
Type declarationsNot declared
Runtime dependency count14
Peer requirement count0
Optional dependency count0
Minified sizeMeasurement not available yet
Minified + gzipMeasurement not available yet
Unpacked distribution size146.15 KiB
Published file count11
Package typeNot declared
ES module entryNot declared
Default entry./lib/forever
Side effects declarationNot declared
Direct advisories0
Resolved graph dependencies293
Repository stars13817
Repository forks932

Install forever 4.0.3

npm install forever@4.0.3
pnpm add forever@4.0.3
yarn add forever@4.0.3

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.

Code-Review3/10 — Found 10/30 approved changesets -- score normalized to 3
Maintained0/10 — 0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
Binary-Artifacts10/10 — no binaries found in the repo
CII-Best-Practices0/10 — no effort to earn an OpenSSF best practices badge detected
Security-Policy0/10 — security policy file not detected
Fuzzing0/10 — project is not fuzzed
License10/10 — license file detected
Branch-Protection0/10 — branch protection not enabled on development/release branches
SAST0/10 — SAST tool is not run on all commits -- score normalized to 0

Evidence and freshness