ps-tree
Get all children of a pid
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
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): ps-tree's core function is to spawn 'ps' to enumerate process trees; child_process usage is fundamental and expected for this package. | ai | |
| dependencies | unvetted-dep:event-stream | AI (dependencies): Pinned to =3.3.4, the last clean release before the malicious event-stream 3.3.6 supply chain attack. This is a deliberate safe pin, not a risk. | ai |
Versions (showing 8 of 8)
| Version | Deps | Published |
|---|---|---|
| 1.2.0 | 1 / 5 | |
| 1.1.1 | 1 / 8 | |
| 1.1.0 | 1 / 8 | |
| 1.0.1 | 1 / 6 | |
| 1.0.0 | 1 / 5 | |
| 0.0.3 | 1 / 0 | |
| 0.0.2 | 1 / 0 | |
| 0.0.1 | 1 / 0 |
v1.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.