68%
Total Score
67
100
90
75
50
No build attestation or trusted-publisher provenance is present, leaving publication origin less independently verifiable. This is a transparency weakness rather than evidence of an unsafe release.
The package has 40 releases over more than 11 years, but no registry release in the last 12 months; the latest release was about 19 months ago. This lowers confidence in current maintenance.
The repository recorded zero commits and zero active maintainers in the last three months. Despite a recent push timestamp, the measured activity suggests maintenance has slowed.
There were two new pull requests in the last month, although none were merged and no issues were closed. This shows limited current activity but is not conclusive abandonment evidence.
The project uses established build tooling and has a real build pipeline, but no security-scanning tools were detected. Build maturity is positive while security-process coverage is limited.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
defu Version ^6.1.4 | — | — |
jiti Version ^2.4.2 | — | — |
citty Version ^0.1.6 | — | — |
scule Version ^1.3.0 | — | — |
knitwork Version ^1.2.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.