Read a project manifest (called package.json in most cases)
91%
Total Score
healthy
Healthy release backed by frequent maintenance, stable versioning, and a highly active project.
The repository name does not match the package and its README does not mention the package, creating a small ownership-transparency concern. However, the package is under the same organization namespace as the linked pnpm monorepo, which makes the mismatch consistent with a subpackage layout.
All 26 workflows were analyzed successfully, all 229 action references are pinned, and no untrusted checkout or script-injection paths were found. The only finding is a high-confidence, low-severity ad hoc package installation in the release workflow, warranting a minor hygiene caution.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
json5 Version ^2.2.3 | — | — |
strip-bom Version ^4.0.0 | — | — |
is-windows Version ^1.0.2 | — | — |
parse-json Version ^5.2.0 | — | — |
@pnpm/error Version 1000.1.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.