Simple monitor script for use during development of a Node.js app.
86%
Total Score
83
94
67
100
One contributor made all 11 commits in the last three months, creating a meaningful continuity risk. The repository is active, which partly offsets but does not remove the concentration concern.
The project uses build tooling, but no security scanning tools were detected. This is a modest transparency and maintenance-process gap rather than evidence of abandonment.
The repository has no security policy, leaving vulnerability reporting and response expectations undocumented.
All five workflows were analyzed with no audit findings or untrusted checkout/script-injection paths, and three use job-level permissions. However, all eight analyzed action references are unpinned, weakening build reproducibility and supply-chain hygiene.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
debug Version ^4 | — | — |
touch Version ^3.1.0 | — | — |
semver Version ^7.5.3 | — | — |
chokidar Version ^3.5.2 | — | — |
minimatch Version ^10.2.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.