74%
Total Score
100
100
85
67
50
No build attestation or trusted-publisher provenance is present, leaving publication origin less transparent. This is a transparency gap, not evidence that the release is unsafe.
The package has seven releases over roughly five years, with no releases in the last 12 months and a latest release nearly two years old. Active repository work partly compensates, but the package release cadence is still slow.
The repository name does not match the package name and its README does not mention the package, creating some uncertainty about package-to-repository correspondence. The mismatch may reflect a monorepo, but the missing README mention warrants caution.
The project uses TypeScript, npm scripts, and SWC for builds, but no security-scanning tools were detected. The build setup is established while security automation is a minor gap.
The repository has no security policy, which makes vulnerability-reporting expectations less clear for adopters.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
tslib Version ^2.8.1 | — | — |
@stoplight/json Version ~3.21.0 | — | — |
@stoplight/yaml Version ~4.3.0 | — | — |
@stoplight/types Version ^14.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.