The README is present and the source repository clearly matches the package, making its purpose and setup understandable. However, the project has had no release or commit activity for over ten years and provides no license or security policy.
32%
Total Score
0
75
75
The latest release was published in February 2016, over ten years ago, and there have been no releases in the last 12 months. This is strong evidence of abandonment despite the package having three historical releases.
There were no commits and no active maintainers in the last three months, consistent with a project that has been inactive for over ten years. This substantially increases abandonment risk.
No license is declared, detected, or included in the package or repository. This creates a material adoption and redistribution risk.
Composer build tooling is present, but no security-scanning tooling is reported. The missing scanning is a secondary hygiene gap rather than the main adoption concern.
The repository has no security policy. For an administration and authentication package, that weakens transparency around handling security reports.
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.