ping
a simple wrapper for ping
1
Versions
MIT
License
No
Install Scripts
Missing
Provenance
Supply chain provenance
Status for the latest visible version.
No SLSA provenance
npm registry signatures
gitHead linked
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
danielzzzmondwan
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| typosquat | typosquat.levenshtein:pino | AI (typosquat): 'ping' is a legitimate, 14-year-old package name for an OS ping wrapper — not a typo of 'pino'. Coincidental Levenshtein proximity; stable false positive for this package. | ai | |
| typosquat | typosquat.levenshtein:pg | AI (typosquat): 'ping' is a legitimate, independent package name unrelated to 'pg'. 2-edit distance match is coincidental; stable false positive for this package. | ai | |
| semgrep | semgrep:child-process-import | AI (semgrep): This package is explicitly a wrapper for the OS ping command; child_process import is the core mechanism and expected for all versions. | ai | |
| semgrep | semgrep:child-process-spawn | AI (semgrep): cp.spawn() is used to invoke the system ping executable — the entire purpose of this library. Expected and stable across all versions. | ai |
Versions (showing 1 of 1)
| Version | Deps | Published |
|---|---|---|
| 1.0.0 | 0 / 28 |
v1.0.0
2 findings
HIGH
typosquat.levenshtein: Possible typosquat of 'pino'
typosquat
Package name 'ping' is 1 edit(s) away from popular package 'pino'.
LOW
No provenance attestation
provenance
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.