This is a healthy, actively maintained release with strong evidence of ongoing development, organizational backing, reproducible npm provenance, stable versioning, and solid package structure. The repository is actively maintained with 145 commits from 11 contributors in the last 3 months, while the package has 23 releases in the last 12 months and no deprecation status. The main concerns are that the package is not named directly in the linked repository README, the repository lacks a security policy, and three workflows grant top-level write permissions; these reduce transparency and hardening but are outweighed by the repository's active maintenance, security scanning, safe workflow analysis, tests, changelog, and organization ownership.
88%
Total Score
100
100
95
80
100
The repository name does not match the package and its README does not mention the package, creating some uncertainty that this specific package is represented by the linked repository; the mismatch may still reflect a monorepo sub-package.
No SECURITY.md policy was found, leaving vulnerability-reporting and response expectations less transparent for dependents.
All workflows declare permissions, but 3 of 8 workflows have top-level write permissions; although no dangerous workflow patterns were detected, narrower permissions would be preferable.
| Dependency | Last Release | Score |
|---|---|---|
diff Version ^8.0.4 | — | — |
ansis Version ^4.3.1 | — | — |
pathe Version ^2.0.3 | — | — |
tinyglobby Version ^0.2.17 | — | — |
@babel/types Version ^7.29.8 | — | — |
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.