The package has a readable README, tests, and a matching source repository. Its license situation is unclear, and the lone maintainer leaves little continuity if development stops.
38%
Total Score
33
69
83
This is the only release, published about 9 years ago, with no releases in the last 12 months. That is strong evidence of abandonment for a dependency.
There were no commits and no active maintainers in the last 3 months, despite the repository's last push being about 4 years ago. This materially increases abandonment risk.
The manifest says to see a LICENSE file, but no license file was found in the package or repository. The package therefore does not clearly provide its stated MIT licensing evidence.
Only one registry maintainer is listed. A single maintainer is not inherently unhealthy, but combined with the inactive repository it leaves little apparent succession capacity.
The package and repository are owned by the same individual account. This is consistent ownership, but it provides less organizational continuity than project backing from an organization.
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.