Node.js module to detect the C standard library (libc) implementation family and version
78%
Total Score
50
100
94
67
100
The repository is owned by an individual rather than an organization, so the single registry maintainer reflects a thin maintainer base and limited visible organizational redundancy.
The repository recorded zero commits and zero active maintainers in the last three months, which is a maintenance caution, though the recent release and non-archived repository provide some compensating evidence.
No build tool or security scanning tool was detected in the repository. This is a modest transparency and maintenance gap for a package with a small codebase.
The repository has no security policy, leaving vulnerability-reporting expectations undocumented.
Both workflows use read-only permissions and the audit completed fully with no dangerous triggers or untrusted checkouts. However, all seven action references are unpinned, and a high-confidence low-severity finding reports an ad hoc package installation outside a lockfile.
We didn't find any vulnerabilities for this package.
No direct dependencies.
Connect your repositories to instantly see whether vulnerable or malicious packages exist in your codebase.
Free. No credit card required.

I consent to receiving marketing communications based on Aikido’s Privacy Policy.
SOC 2Compliant
ISO 27001Compliant
ISO 42001Compliant© All Intel data is openly available and commercially licensed.