The project is small and lightly active, with no security scanning or published security policy. Its README and recent repository push provide useful transparency, but the release remains a poor dependency choice.
20%
Total Score
50
64
75
Packagist marks the entire package as abandoned, with no distinct replacement identified. Package-level deprecation is a severe dependency risk even though the repository remains available.
The release includes a license file and repository license, so it is licensed, but the manifest declares GPL-2.0-or-later while the detected file identifies GPL-3.0. That mismatch warrants clarification.
The package has only 3 releases over 719 days, with 2 releases in the last 12 months and a median interval of about 248 days. This indicates a small, infrequently released project rather than mature release activity.
The repository recorded 0 commits and 0 active maintainers in the last 3 months, although the latest push was recent. The lack of recent development activity limits confidence in ongoing maintenance.
Composer build tooling is present, but no security-scanning tool was detected. This weakens supply-chain hygiene without proving the release is unsafe.
We didn't find any vulnerabilities for this package.
No maintainer information available.
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.