A single maintainer, no license, and no security policy leave limited transparency and continuity. The package is small and clearly documented, but its maintenance capacity is weak.
35%
Total Score
50
50
83
No declared license, license file, or repository license file was found. That creates a material adoption and redistribution problem rather than a cosmetic gap.
The latest release was in January 2016, with no releases in the last 12 months and only four releases overall. This is strong evidence of abandonment risk for a package a developer would depend on.
Only one registry maintainer is listed. Because the project is user-owned rather than organization-backed, this leaves a thin continuity base.
The package and repository are owned by the same individual account, confirming ownership alignment but not organizational backing or broader maintenance capacity.
The repository has one star, zero forks, and one watcher. Popularity is supporting evidence rather than a verdict, but these values provide no meaningful external maturity signal.
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.