The README, tests, stable versioning, and small dependency set make the package straightforward to evaluate and use. Its single-maintainer project has shown no releases or commits for nearly two years, and the repository lacks security scanning and a security policy.
55%
Total Score
50
100
83
75
One registry maintainer is responsible for publishing the package, leaving a thin operational base. The linked repository is user-owned rather than organization-backed, so no broader backing is shown to offset that concentration.
The package has had no releases in the last 12 months, and its latest release was nearly two years before this assessment. That weakens confidence that compatibility and defects will be addressed.
The repository recorded zero commits and zero active maintainers in the last three months, consistent with a project that is currently dormant. The non-archived status does not compensate for the lack of observed activity.
Composer is used for the build, which is appropriate, but no security-scanning tool was detected. That is a modest hygiene gap rather than evidence that the release is unsafe.
The repository has no security policy. This is a transparency and response-process gap, though it is less severe for this small library than for a package handling credentials or network infrastructure.
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.