forever-monitor
Core forever process monitor
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| semgrep | semgrep:child-process-import | AI (semgrep): forever-monitor's core purpose is spawning and monitoring child processes; child_process usage is fundamental and expected for this package. | ai | |
| semgrep | semgrep:env-bulk-read | AI (semgrep): Reading process.env to forward environment variables to managed child processes is standard behavior for a process supervisor. | ai |
Versions (showing 5 of 5)
| Version | Deps | Published |
|---|---|---|
| 3.0.3 | 5 / 7 | |
| 3.0.2 | 5 / 7 | |
| 3.0.1 | 5 / 7 | |
| 3.0.0 | 5 / 7 | |
| 2.0.0 | 5 / 6 |
v3.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.