The codebase is small and documented, and its package name matches the repository. Composer is the only build tool, with no install-time scripts or security policy, so ongoing maintenance and security transparency are limited.
42%
Total Score
50
81
75
The package has had no release in about 3 years and 4 months, with zero releases in the last 12 months. That sustained silence is a substantial abandonment concern.
Only one registry publishing maintainer is listed, and project_backing identifies an individual owner rather than an organization. This leaves limited visible publishing capacity if the maintainer becomes unavailable.
The repository recorded zero commits and zero active maintainers in the last 3 months, consistent with the long release gap. The repository is not archived, but current maintenance is not demonstrated.
Composer build tooling is present, but no security-scanning tools were detected. That is a modest transparency and maintenance weakness for a package intended for application integration.
The linked repository has no security policy. This weakens the documented path for reporting and handling vulnerabilities, though it does not by itself show that the package is unsafe.
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.