Write a project manifest (called package.json in most cases)
88%
Total Score
healthy
Healthy: steady releases and a very active, well-backed source project outweigh minor workflow and repository-identification cautions.
The linked repository name does not match the package and its README does not mention this package, creating some uncertainty about package-to-repository mapping. The package is part of an organization-owned monorepo, which partly mitigates that concern.
All 26 workflows were analyzed, all 229 action references are pinned, and no untrusted checkout or script-injection issues were found. One high-confidence, low-severity adhoc-packages finding in the release workflow is a minor hygiene concern.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
json5 Version ^2.2.3 | — | — |
@pnpm/types Version 1001.3.0 | — | — |
write-yaml-file Version ^5.0.0 | — | — |
write-file-atomic Version ^5.0.1 | — | — |
@pnpm/text.comments-parser Version 1000.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.