detect-libc
Node.js module to detect the C standard library (libc) implementation family and version
Supply chain provenance
Status for the latest visible version.
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): detect-libc's core purpose is to detect the system libc by running shell commands; child_process import is intentional and documented functionality, not a risk. | ai | |
| semgrep | semgrep:child-process-exec | AI (semgrep): exec() is used to run ldd and similar system commands to detect libc — this is the package's primary function, not malicious behavior. | ai |
v2.1.1
2 findingsThis version was published by a different npm account than previous versions on 2025-09-24. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.1.0
2 findingsThis version was published by a different npm account than previous versions on 2025-09-14. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.