The MIT license, matching repository, and lack of install-time scripts improve transparency and reduce integration risk. The minimal README, solo ownership, and missing security policy provide limited guidance and oversight.
55%
Total Score
50
70
50
Only one registry account has publish access. The linked repository is also owned by an individual rather than an organization, leaving a thin operational and succession base.
The package includes a README, but it is only 13 characters long and offers almost no consumer guidance. Missing tests and changelog files are normal for a published package artifact and are not concerns here.
Only two releases exist, and none were published in the last 12 months; the latest release was about two years ago. This indicates a small, potentially inactive project rather than an established release process.
There were no commits and no active maintainers in the last three months, consistent with the repository having last been pushed about two years ago. This is the strongest evidence of reduced maintenance capacity.
The repository has no published security policy. For a code library, that weakens the transparency around vulnerability reporting and response.
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.