output coverage reports using Node.js' built in coverage
72%
Total Score
50
95
75
50
No build attestation or trusted-publisher provenance is available, leaving the relationship between source and published artifact less transparent.
The repository owner is an individual account, so there is no organizational backing shown to offset the concentrated recent maintenance activity.
All recent commit activity comes from one contributor, so maintenance depends heavily on a single active person; the project backing is an individual account rather than an organization.
Only 1 commit was made in the last 3 months, indicating a sharply limited recent maintenance pace despite the recent release and repository push.
There are 3 new issues and 4 new pull requests in the last month, but none were closed or merged, suggesting limited recent throughput.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
yargs Version ^18.0.0 | — | — |
find-up Version ^5.0.0 | — | — |
test-exclude Version ^8.0.0 | — | — |
yargs-parser Version ^21.1.1 | — | — |
v8-to-istanbul Version ^9.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.