The stable package has a clear README, matching MIT licensing, and organizational ownership. Its single maintainer, absent security policy, and no commits or releases since September 2017 leave maintenance and vulnerability response uncertain.
42%
Total Score
50
81
75
The latest release was published in September 2017, and there have been no releases in roughly nine years. This is strong evidence of abandonment risk for a dependency expected to receive maintenance.
There were no commits and no active maintainers in the last three months, consistent with the roughly nine-year release gap and materially increasing abandonment risk.
Only one registry publishing account is listed, which is a thin publishing base. The organization-backed repository partly compensates, but it does not show active maintenance.
Composer is used as a build tool, showing some project structure, but no security scanning tooling is configured. This is a moderate transparency and maintenance gap, not a severe risk alone.
The repository has no security policy, so users have no documented vulnerability-reporting process. The long inactivity makes this gap more consequential.
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.