This project serves as a converter between the legacy ruleset format and a new one. It's used internally, albeit it can be used externally too, also in browsers.
82%
Total Score
healthy
Healthy release with active maintenance; workflow credential sharing and weak package-to-repository identification are the main caveats.
No build attestation or trusted-publisher identity is present, which reduces publication transparency, although the active repository and release history provide compensating maintenance evidence.
The repository name differs from the package name, which is ordinary for a monorepo, but its README does not mention this package; that weakens confidence that the linked repository specifically documents and owns this package.
The repository uses TypeScript, npm scripts, and SWC for builds, but no security-scanning tools were detected, leaving a modest security-process gap.
The repository has no security policy, reducing transparency for reporting and handling vulnerabilities despite the otherwise active project.
All six workflows were analyzed, with no untrusted checkouts or script injection. However, 18 of 20 action references are unpinned, one reusable workflow inherits secrets with medium high-confidence severity, and one workflow installs a package outside a lockfile.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
ajv Version ^8.18.0 | — | — |
tslib Version ^2.8.1 | — | — |
astring Version ^1.9.0 | — | — |
reserved Version 0.1.2 | — | — |
ast-types Version 0.14.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.