Additional ESLint's rules for Node.js
42%
Total Score
33
80
67
50
The package has 60 releases but none in the last 12 months, and its latest registry release was in March 2020. That long release gap is a substantial maintenance and compatibility concern.
The repository recorded zero commits and zero active maintainers in the last three months. This strongly supports the conclusion that active maintenance has stopped or is very limited.
No build attestation or trusted-publisher configuration was observed. This weakens publication transparency, but the package is otherwise clearly identified and this alone does not establish that the release is unsafe.
Only one registry account has publish access. The linked repository is user-owned rather than organization-backed, so there is little visible redundancy in publishing or maintenance capacity.
There were no new or closed issues and no merged pull requests in the last month, despite 106 open issues and 22 open pull requests. This indicates an inactive maintenance queue.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
ignore Version ^5.1.1 | — | — |
semver Version ^6.1.0 | — | — |
resolve Version ^1.10.1 | — | — |
minimatch Version ^3.0.4 | — | — |
eslint-utils Version ^2.0.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.