Settle promises concurrently and get their fulfillment value or rejection reason with optional limited concurrency
78%
Total Score
63
100
94
88
50
No build attestation or trusted-publisher provenance is present, leaving publication origin less independently verifiable; this is a transparency gap rather than evidence of unsafe code.
One registry publishing account is a narrow operational base, although the linked repository and release history provide compensating evidence of established ownership.
The repository is owned by a named individual rather than an organization, so the single registry maintainer reflects a genuinely narrow maintainer base.
The repository has had zero commits and zero active maintainers in the last three months. The recent release partly offsets this, but the quiet source history raises a maintenance caution.
No build tool or security scanning tool was detected. This is a modest project-hygiene gap, partly offset by the repository's simple file layout and security policy.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
p-limit Version ^4.0.0 | — | — |
p-reflect Version ^3.1.0 | — | — |
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.