@pm2/agent
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:nssocket | AI (phantom-deps): nssocket is a real transport dependency used dynamically; stable FP for this package. | ai | |
| semgrep | semgrep:child-process-spawn | AI (semgrep): spawn() is used to launch the PM2 interactor daemon as a detached child process — core functionality of a process manager agent, not malicious. | ai | |
| semgrep | semgrep:child-process-exec | AI (semgrep): exec() in WatchDog.js resurrects PM2 via its own binary path — expected watchdog behavior for a process manager agent. | ai | |
| semgrep | semgrep:child-process-import | AI (semgrep): child_process import is required for PM2 agent's process management functionality; matches public source code. | ai | |
| semgrep | semgrep:dynamic-require | AI (semgrep): Dynamic require resolves a static relative config path via path.join(__dirname, '../config') — not user-controlled, not a security risk. | ai |
Versions (showing 7 of 7)
| Version | Deps | Published |
|---|---|---|
| 2.1.1 | 12 / 4 | |
| 2.1.0 | 12 / 4 | |
| 2.0.4 | 13 / 4 | |
| 2.0.3 | 13 / 4 | |
| 2.0.2 | 13 / 4 | |
| 2.0.1 | 13 / 4 | |
| 2.0.0 | 13 / 4 |
v2.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.1
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.