It has a clear MIT license, minimal runtime dependencies, tests, documentation, and release notes. The single maintainer, no security scanning, and fully unpinned CI actions leave modest long-term and build-hygiene concerns.
77%
Total Score
50
100
94
83
Only one registry account has publish access. Because the project is user-owned rather than organization-backed, this leaves a thinner publishing and continuity base.
The registry namespace and repository are owned by the same individual, and the repository is user-owned rather than organization-backed. This is coherent ownership, but it does not provide evidence of a broader support organization.
There were no commits and no active maintainers in the last three months. The same-day release update offsets immediate abandonment concerns, but ongoing maintenance capacity is not demonstrated.
Composer build tooling is present, but no security scanning tools were detected. For a small client this is a hygiene gap rather than evidence of abandonment.
The repository has no security policy. This reduces transparency about vulnerability reporting and handling, although the release includes tests and clear documentation.
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.