Chrome Debugging Protocol interface
68%
Total Score
50
100
89
50
50
No build attestation or trusted-publisher identity is present, reducing release transparency even though this alone does not indicate an unsafe package.
A prepare script runs during installation, which adds execution surface; the signal does not show that it performs unsafe or unusual work.
Only one registry account has publish access, creating a limited publishing base; the linked repository confirms an individual owner rather than organizational backing.
The source repository is owned by an individual account, so there is no organization backing shown to compensate for the single registry maintainer.
The project is mature, with 79 releases since 2013, but only one release in the last 12 months; the long median interval is less concerning because a current release exists.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
ws Version ^7.2.0 | — | — |
commander Version 2.11.x | — | — |
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.