safeps
Work with processes safely and easily with Node.js
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): safeps is explicitly a child_process wrapper library; importing child_process is its core functionality, not a risk signal. | ai | |
| semgrep | semgrep:child-process-execsync | AI (semgrep): execSync usage is for checking binary executability (running --version), which is the documented safe process inspection purpose of this library. | ai |
Versions (showing 51 of 61)
| Version | Deps | Published |
|---|---|---|
| 11.6.0 | 5 / 15 | |
| 11.5.0 | 5 / 15 | |
| 11.4.0 | 5 / 17 | |
| 11.3.0 | 5 / 17 | |
| 11.2.0 | 5 / 17 | |
| 11.1.0 | 5 / 17 | |
| 11.0.0 | 5 / 17 | |
| 10.18.0 | 4 / 13 | |
| 10.17.0 | 4 / 13 | |
| 10.16.0 | 4 / 13 | |
| 10.15.0 | 4 / 13 | |
| 10.14.0 | 4 / 13 | |
| 10.13.0 | 4 / 13 | |
| 10.12.0 | 4 / 13 | |
| 10.11.0 | 4 / 13 | |
| 10.10.0 | 4 / 13 | |
| 10.9.0 | 4 / 13 | |
| 10.8.0 | 4 / 13 | |
| 10.7.0 | 5 / 13 | |
| 10.6.0 | 4 / 14 | |
| 10.5.0 | 4 / 14 | |
| 10.4.0 | 4 / 14 | |
| 10.3.0 | 4 / 14 | |
| 10.2.0 | 4 / 14 | |
| 10.1.0 | 4 / 14 | |
| 10.0.0 | 4 / 14 | |
| 9.3.0 | 4 / 13 | |
| 9.2.0 | 4 / 13 | |
| 9.1.0 | 4 / 13 | |
| 9.0.0 | 4 / 13 | |
| 8.1.0 | 5 / 17 | |
| 8.0.0 | 5 / 17 | |
| 7.0.1 | 5 / 9 | |
| 7.0.0 | 5 / 9 | |
| 6.4.0 | 5 / 9 | |
| 6.3.0 | 5 / 9 | |
| 6.2.0 | 5 / 9 | |
| 6.1.0 | 5 / 9 | |
| 6.0.2 | 5 / 8 | |
| 6.0.1 | 5 / 8 | |
| 6.0.0 | 4 / 7 | |
| 5.1.0 | 4 / 6 | |
| 5.0.0 | 4 / 6 | |
| 4.0.0 | 4 / 5 | |
| 3.0.2 | 4 / 5 | |
| 3.0.1 | 4 / 5 | |
| 3.0.0 | 4 / 5 | |
| 2.2.13 | 4 / 5 | |
| 2.2.12 | 4 / 5 | |
| 2.2.11 | 4 / 5 | |
| 2.2.10 | 4 / 5 |
v11.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.18.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.17.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.16.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.15.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.14.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.13.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.12.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.11.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.10.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.9.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.