node-redlock
A distributed locking algorithm used to manage distributed resources in a system.
62%
Total Score
25
100
85
67
50
Health Score Breakdown
There were no commits and no active maintainers in the last three months, which is a meaningful maintenance warning despite the recent release.
No build attestation or trusted-publisher identity is present, so consumers have less verifiable evidence connecting the published artifact to its source build.
Only one registry account can publish the package, leaving limited publishing capacity and increasing the impact of maintainer unavailability.
The package has existed for about 4 years and released version 2.3.0 recently, but only one release appeared in the last 12 months, indicating a slow cadence.
The repository has only 3 stars, 0 forks, and 1 watcher. Popularity is supporting evidence rather than a verdict, but these figures provide little external resilience signal.
Vulnerabilities
| Title | Versions | Severity |
|---|---|---|
AIKIDO-2025-10835 Pre-CVE Found by Aikido Intel before public disclosure or CVE publication. node-redlock is vulnerable to Insecure Randomness in versions 1.1.0 - 2.2.1. | 1.1.0 - 2.2.1 | Low |
Package versions
Maintainers
Direct Dependencies
| Dependency | Last Release | Score |
|---|---|---|
 redis Version ^4.6.14 | — | — |
ioredis Version ^5.4.1 | — | — |
Weekly Downloads
Info
- Last Published
- 10 months ago
- Created
- 2 years ago
- Unpacked Size
- 0.2 MB
Are You Affected?
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 27001CompliantISO 42001Compliant
FedRAMPImplementing© All Intel data is openly available and commercially licensed.