General purpose node utilities
82%
Total Score
67
100
94
75
50
No build attestation or trusted-publisher provenance is present, leaving publication origin less independently verifiable. The otherwise clear package structure and repository link partly offset this transparency gap.
All three recent commits came from one contributor, so short-term maintenance is concentrated. Organization ownership provides some handoff capacity, but no second recent contributor is shown.
The repository had three commits in the last three months, showing recent activity, but only one active maintainer contributed them, limiting evidence of broad ongoing maintenance.
The project uses TypeScript, Vitest, and npm scripts, but no security scanning tool was detected; this is a modest transparency and hygiene gap rather than evidence of abandonment.
The sole workflow was fully analyzed with no audit findings or untrusted-code sinks, but its one action use is unpinned, leaving the build exposed to action-reference changes.
| Title | Versions | Severity |
|---|---|---|
CVE-2020-36604 @hapi/hoek is vulnerable to Improperly Controlled Modification of Object Prototype Attributes ('Prototype Pollution') in versions 0.0.0 - 8.5.1 and 9.0.0 - 9.0.3. | 0.0.0 - 8.5.19.0.0 - 9.0.3 | High |
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.