A gorgeous reporter for Mocha.js
88%
Total Score
80
100
94
70
100
The package uses a prepare install-time script, which adds some installation complexity and supply-chain exposure, though no dangerous behavior is shown by this signal alone.
Only one registry account has publish access, creating publishing continuity risk; however, repository activity shows three active contributors, which partly compensates for the narrow registry maintainer list.
The repository is owned by an individual rather than an organization, so the active three-person contributor base provides useful but limited continuity backing.
No build tool or security scanning tool was detected. This is a transparency and process gap, though the active repository, tests, and npm provenance provide meaningful compensating evidence.
The repository has no security policy, leaving vulnerability-reporting expectations unclear and reducing security transparency.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
diff Version ^5.2.0 | — | — |
json-stringify-safe Version ^5.0.1 | — | — |
mochawesome-report-generator Version ^6.3.2 | — | — |
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.