88%
Total Score
healthy
Healthy: frequent releases and active, well-distributed repository maintenance outweigh workflow hygiene concerns.
No build attestation or trusted-publisher provenance was recorded, reducing release transparency even though the package has an active release history and repository.
The project uses TypeScript, npm scripts, and SWC, but no security-scanning tools were detected. This is a modest transparency gap rather than evidence of abandonment.
The repository has no documented security policy, leaving vulnerability-reporting expectations unclear for users of the package.
All six workflows were analyzed with no high-severity findings, but 18 of 20 action references are unpinned and the audit found high-confidence secrets-inherit and adhoc-packages issues. These are workflow hygiene concerns, not a standalone adoption blocker.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
ajv Version ^8.18.0 | — | — |
leven Version 3.1.0 | — | — |
tslib Version ^2.8.1 | — | — |
lodash Version ^4.18.1 | — | — |
ajv-formats Version ~2.1.1 | — | — |
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.