The project has a long release history, a clear license, documented usage, and repository tests. Recent repository activity is absent, the project has one registry maintainer, and its two workflow actions are unpinned; there is also no security policy.
68%
Total Score
50
100
94
83
Only one account has registry publish access. That is a limited publishing base for a user-owned project and increases continuity risk if that maintainer becomes unavailable.
The repository is owned by the same individual namespace as the package, so the source and registry identity are aligned; it is not organization-backed, leaving a narrow ownership base.
The repository recorded zero commits and zero active maintainers in the last three months. Although the recent release provides some compensating evidence, the current maintenance signal is quiet.
Composer build tooling is present, but no security scanning tools were detected. For a small library this is a hygiene gap rather than evidence of abandonment.
The repository has no security policy, leaving vulnerability-reporting expectations undocumented for consumers.
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.