Tests, release notes, a clear MIT license, and no install scripts make the artifact easier to assess. The absence of security scanning and a security policy adds a smaller transparency concern.
44%
Total Score
25
100
75
75
The package has had only three releases, all concentrated on October 31, 2021, with no release in nearly five years. This is strong evidence of abandonment risk, despite the stable 1.0.2 version.
The repository recorded no commits and no active maintainers in the last three months, while its last push was more than four years ago. The repository is not archived, but current maintenance capacity appears absent.
One registry publishing account provides a thin maintainer base. Because the repository is user-owned rather than organization-backed, there is little visible redundancy if that maintainer stops responding.
The repository has zero stars, one fork, and one watcher, providing little supporting evidence of broad review or community resilience. Popularity is only supporting evidence, so this reinforces rather than determines the maintenance concern.
The repository has no security policy and no security scanning tools. This weakens vulnerability-reporting and review transparency, though it is less serious than the prolonged inactivity.
We didn't find any vulnerabilities for this package.
No direct dependencies.
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.