The organization-backed repository matches the package and provides a substantial README plus release notes. The declared GPL-3.0 conflicts with the detected GPL-2.0 license, while workflow template-injection findings and absent security tooling add maintenance and release-hygiene concerns.
58%
Total Score
67
100
79
67
A license file is present, but it identifies GPL-2.0 while the manifest declares GPL-3.0. That mismatch should be resolved before relying on the release's licensing terms.
The package has existed since July 2019 with 20 releases, but it had no releases in the last 12 months, which is a meaningful sign of slowing maintenance.
There were no commits and no active maintainers in the last three months. This is a concrete maintenance concern, even though the repository is not archived.
There were no newly opened or closed issues in the last month, and one pull request was opened without a merge, suggesting limited recent project movement.
The repository uses Composer, but no security scanning tools were detected. That is a modest transparency and maintenance gap rather than evidence that the package is unsafe.
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.