Generate multiple mocha reports in a single mocha execution.
72%
Total Score
63
100
95
90
50
No build attestation, trusted publisher, or staged publishing is present. This reduces release transparency and makes artifact provenance harder to verify, though it is not evidence that the release is malicious.
Two registry accounts have publish access. This is a modest publishing base, but registry access alone does not establish active maintenance and is outweighed here by the repository activity evidence.
The repository is owned by an individual user rather than an organization. Individual ownership is not inherently unhealthy, but it provides less visible institutional backing and increases reliance on a small maintainer base.
There were 0 commits and 0 active maintainers in the last 3 months. Although a release and repository push occurred recently, the lack of observed commit activity is a meaningful maintenance-continuity concern.
The repository reports no build tooling and no security scanning tools. This is a transparency and process gap, although the package is small and has a straightforward source layout.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
debug Version ^4.1.1 | — | — |
lodash Version ^4.17.15 | — | — |
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.