The package has organization backing, a stable version, a matching repository, and no install-time scripts. Its missing license and security policy reduce transparency, while the lack of security scanning leaves maintenance safeguards unclear.
58%
Total Score
75
79
75
Neither the package metadata nor the collected repository contains a recognized license declaration or license file. That creates a real legal and transparency gap for adoption.
The package has five releases since February 2021, but none in the last 12 months and the latest was published in November 2023. This indicates a mature but currently inactive release stream.
The repository recorded zero commits and zero active maintainers in the last three months, consistent with no recent registry releases. This raises maintenance and abandonment concerns, though the repository is not archived.
Composer build tooling is present, but no security-scanning tools were detected. The missing automated security check modestly lowers confidence in the project's maintenance hygiene.
The repository has no security policy, so there is no documented process for reporting or handling vulnerabilities. This is a transparency weakness rather than evidence of unsafe code.
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.