The project has had no release or commit activity since January 2023, and only one registry maintainer is listed. It also has no license and the repository does not clearly match the package name, which makes long-term ownership and reuse harder to verify.
38%
Total Score
25
38
50
The package has only 3 releases, all concentrated in January 2023, with no releases in the last 12 months and a package age of about 3 years 8 months. This is strong evidence of abandonment for a framework dependency.
The repository recorded 0 commits and 0 active maintainers in the last 3 months, consistent with the release history showing no activity since January 2023. No provided signal shows ongoing maintenance capacity.
No declared license or license file was found in the package or repository. That creates a concrete reuse and legal-transparency concern for a dependency.
Only one registry maintainer is listed. A single maintainer increases continuity risk, especially alongside the absence of recent releases and commits.
The repository name does not match the package name, and the README does not provide a package mention. A name mismatch can be normal for a sub-package, but no provided evidence confirms that relationship here.
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.