The stable release and straightforward Composer packaging provide some reassurance. Long-term inactivity, missing licensing, and limited project documentation make future maintenance and adoption a liability.
39%
Total Score
50
67
88
The package has had only two releases, both in December 2022, and none in the last 12 months. This long release gap is strong evidence of abandonment risk.
The repository recorded zero commits and zero active maintainers in the last three months, consistent with the unchanged release history and indicating no observable ongoing maintenance.
No license is declared, and neither the package nor repository contains a detected license file. This creates a material legal and adoption risk for dependents.
One registry maintainer is listed. For an individually owned project this is consistent with the repository ownership, but it leaves little redundancy if that maintainer stops working.
The artifact has no README, while tests and a changelog are normally repository concerns and are not expected in every published artifact. The missing consumer-facing documentation is still a minor transparency gap for a framework library.
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.