Tests, a clear README, and a matching source repository make the package straightforward to evaluate. Its single maintainer and roughly seven years without commits or releases reduce confidence that future compatibility or defects will be addressed.
58%
Total Score
50
100
88
75
Only one registry maintainer is listed, leaving limited publishing redundancy. The matching user-owned repository and the package's small scope provide some compensation, but not much backup capacity.
The registry namespace and repository belong to the same individual account, providing clear ownership but no organizational backing or maintainer redundancy.
The package has had no release in roughly seven years, with zero releases in the last 12 months. Its five-release history shows a mature stable package, but the long pause raises abandonment concerns.
There were no commits and no active maintainers in the last three months, consistent with the roughly seven-year release gap. This is the strongest evidence that future fixes may not arrive.
The repository uses Composer and Phing for builds, which supports reproducibility, but it has no reported security-scanning tooling. For this small library that is a hygiene gap rather than a severe risk.
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.