The stable 1.0.2 release includes release notes and the repository is active and organization-backed. Its empty README, absent security policy, and lack of security scanning leave limited guidance and assurance for adopters.
72%
Total Score
75
100
71
75
The manifest declares GPL-2.0-or-later and the repository license file was detected as GPL-2.0; the recognized repository license does not exactly match the declaration, creating a small licensing clarification concern.
The package includes a release note for version 1.0.2, but its README is empty and there are no tests or changelog; the release note compensates for the missing changelog, while the empty README limits integration guidance.
The package has three releases, all published on the same day, so it shows initial publishing activity but not an established release track record.
There were no commits or active maintainers in the three-month activity window. Because the package is only zero days old in the collected release history, this is limited evidence of abandonment rather than a severe maintenance collapse.
Composer build tooling is present, but no security scanning tools were detected, leaving a modest gap in the project's security assurance process.
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.