Tests, documentation, licensing, and a focused dependency profile are in place. The small project has no security policy or scanning, leaving limited evidence of continued support; pinning this version is prudent.
39%
Total Score
50
100
72
50
Only two releases were published, both in November 2016, with no release in nearly 10 years. This is strong evidence of abandonment despite the package not being deprecated.
The registry namespace and repository owner match, and the owner is an individual user rather than an organization. This is consistent ownership, but it offers limited backing capacity.
The repository has 2 stars and 0 forks, providing little supporting evidence of community review or shared maintenance. Low popularity is not decisive for a small focused library, but it adds uncertainty alongside the stale release history.
Composer build tooling is present, but no security scanning tools were detected. That leaves release hygiene less demonstrable for a package whose repository has already been inactive for years.
The repository has no security policy, so there is no documented process for reporting or handling vulnerabilities. This is a transparency and maintenance gap, though not severe on its own.
We didn't find any vulnerabilities for this package.
No maintainer information available.
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.