The implementation is small and clearly tied to its source repository, with MIT licensing and no install-time scripts. Its README is only a title, and there are no tests or security scanning tools to support future maintenance.
48%
Total Score
75
81
75
A README is present, but it contains only the package title and gives consumers no usage guidance. The absence of tests and a changelog in the published artifact is normal packaging practice, while no repository tests were observed.
This is the only release, published over eight years ago, with no releases in the last 12 months. That strongly limits evidence of ongoing maintenance and increases abandonment risk.
There were no commits and no active maintainers in the last three months. Combined with the one-release history, this is strong evidence that maintenance has stopped.
Composer is used for the build, but no security scanning tools are configured. This is a maintenance and hygiene gap, though not by itself evidence that the package is unsafe.
The repository has no security policy, leaving no documented channel or process for handling vulnerabilities. This lowers transparency for a package that may remain in use for years.
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.