Build environment checking (a la autoconf) for node.js
64%
Total Score
50
100
80
67
50
No build attestation or trusted-publisher provenance is reported, limiting publication transparency, although this is a transparency gap rather than evidence of a bad release.
Only one registry publishing account is listed, so publishing and maintenance capacity are concentrated in a single person; the linked repository is also user-owned rather than organization-backed.
The source is backed by an individual account rather than an organization, so there is no demonstrated organizational continuity to offset the single-maintainer concentration.
There were no commits and no active maintainers in the last three months. The recent release is a compensating sign, but current development activity remains quiet.
There is one open issue and no issue or pull-request activity in the last month, offering little evidence of active community review.
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.