Its packaging is clear, dependency-light, and actively released, with an organization-backed repository. The declared GPL-3.0-or-later license conflicts with the detected MIT license, while recent work comes from one contributor and workflows lack pinned actions and security scanning.
68%
Total Score
67
100
86
67
The manifest declares GPL-3.0-or-later, but the artifact license file is detected as MIT; both are present, so the release is licensed, yet the mismatch needs resolution before adoption.
One contributor made all 8 recent commits, creating concentration risk; organization ownership provides some handoff capacity but does not remove the thin recent contributor base.
The repository received 8 commits in the last 3 months, showing current work, but all activity came from one active maintainer.
Composer build tooling is present, but no security-scanning tool was detected, leaving a meaningful review and monitoring gap.
The linked repository has no security policy, reducing transparency about how vulnerabilities should be reported and handled.
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.