The project is actively maintained and publishes with provenance, but its issue backlog is growing faster than it closes. Workflow permissions and the repository's failure to identify this package add meaningful transparency and operational concerns.
65%
Total Score
90
100
83
75
100
The repository is receiving new issues and pull requests, but 59 new issues versus 4 closed in the last month and 515 open issues indicate a substantial unresolved backlog.
The repository name does not match the package and its README does not mention the package, so the linkage is not independently clear; although monorepo name mismatches are normal, both checks failing is a transparency concern.
The project uses TypeScript, Vitest, Turbo, and npm scripts, but no security-scanning tooling was detected, leaving a modest security-process gap.
No repository security policy was found, reducing transparency about vulnerability reporting and response expectations.
Version 1.4.4 is a stable, non-prerelease release on a stable major line, although the recent prerelease share is reported as 100%, which weakens confidence slightly.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
js-yaml Version 4.2.0 | — | — |
@jsdevtools/ono Version 7.1.3 | — | — |
@types/json-schema Version 7.0.15 | — | — |
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.