Calculate meta-vulnerabilities from package security advisories
68%
Total Score
63
100
94
88
100
All one recent commit came from a single contributor, concentrating current activity; organization ownership makes handoff more plausible than for an unaffiliated project, but does not remove the maintenance concern.
The repository recorded only one commit in the last three months, which is sparse for an actively maintained dependency, although the recent release and organization backing provide some compensation.
Only two issues and three pull requests are open, but there were no new or closed issues or merged pull requests in the last month, providing little evidence of current activity.
No type declarations are published, which makes integration less convenient for TypeScript consumers, though this is a consumer-ergonomics gap rather than an abandonment signal.
All eight workflows were analyzed, but all 38 action references are unpinned and four workflows grant top-level write permissions. High-confidence template-injection findings and a medium-confidence bot-condition finding add workflow hygiene risk, though no untrusted checkout or script-injection sink was found.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
pacote Version ^22.0.0 | — | — |
semver Version ^7.3.5 | — | — |
cacache Version ^21.0.1 | — | — |
proc-log Version ^7.0.0 | — | — |
json-parse-even-better-errors Version ^6.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.