Map-like, concurrent promise processing for Node.js
82%
Total Score
88
100
95
75
50
No build attestation or trusted-publisher provenance is available, leaving publication origin less transparent. This is a hygiene gap, not evidence that the release is unsafe.
The repository had zero commits from active maintainers in the last three months. The recent release and push date compensate partly, but the quiet development window lowers maintenance confidence.
The project uses TypeScript and npm build tooling, but no repository security-scanning tools were detected. This is a modest transparency and hygiene gap.
The repository has no security policy, leaving vulnerability reporting and response expectations undocumented.
The single workflow was fully analyzed with no dangerous triggers, untrusted checkouts, script injection, or audit findings. Both action references are unpinned, which weakens build reproducibility and warrants a minor caution.
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.