Consumers get little documentation or project-level assurance. The package has not changed since its initial release burst, so maintenance and future compatibility are uncertain.
38%
Total Score
33
56
75
No license is declared, and neither the package nor the collected repository contains a license file. This leaves developers without clear permission to use, modify, or redistribute the code.
The package has had only 3 releases, all clustered on February 13, 2023, with no releases in the following 12 months despite being over 3 years old. This is strong evidence of abandonment risk.
There were 0 commits and 0 active maintainers in the last 3 months. Together with the old last push and release history, this materially increases abandonment risk.
Only one registry maintainer is listed. For an individually owned project this is not inherently abnormal, but it leaves little apparent publishing redundancy when combined with absent recent activity.
The package has no README, tests, or changelog; while tests and changelogs are normally repository concerns, the missing README is a real documentation gap for a framework library. A GitHub release exists for this version, providing some release traceability.
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.