Risky to adopt: the package has strong historical structure and licensing, but it appears effectively abandoned, with no release or repository activity for about nine years. Its low popularity and lack of a security policy add uncertainty for a dependency today.
38%
Total Score
0
67
50
The package has a substantial history with 234 releases, but its latest release was in June 2017 and there have been no releases in roughly nine years. That long release gap is a serious maintenance concern.
The repository recorded zero commits and zero active maintainers over the last three months, consistent with the release history showing no recent maintenance. No stronger activity signal compensates for this inactivity.
The repository has zero stars and forks and only one watcher. Popularity is not decisive by itself, but these very low figures provide no supporting evidence of an active user or contributor community.
Composer build tooling is present, showing basic project setup, but no security scanning tools were detected. This is a modest hygiene gap rather than evidence that the release is unsafe.
The repository has no security policy. For an old package with no recent maintenance, the absence of a documented vulnerability-reporting path increases uncertainty.
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.