A node.js redlock implementation for distributed redis locks
62%
Total Score
50
100
90
50
50
No build attestation or trusted-publisher identity is present, reducing release transparency. This is a supply-chain hygiene gap rather than evidence that the release is unsafe.
The package runs a prepare lifecycle script during installation. This is not inherently unsafe, but it adds install-time behavior that should be understood when using a prerelease dependency.
The registry lists one publishing account. The linked repository is user-owned rather than organization-owned, so the narrow publisher base provides limited redundancy.
The package has existed since 2015 with 27 releases, but it has had no registry release in the last 12 months; the latest release is from March 2022. This materially raises maintenance and abandonment concerns.
There were zero commits and zero active maintainers in the three months measured, indicating that active development has currently stalled despite the repository not being archived.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
node-abort-controller Version ^3.0.1 | — | — |
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.