The release is licensed, documented, tested, and has no install-time scripts. Organization backing and a matching repository add transparency, but the single registry maintainer and inactive development reduce confidence for a new dependency.
58%
Total Score
50
79
75
There were zero commits and zero active maintainers in the last three months, consistent with a project that has stopped evolving. This raises maintenance and abandonment risk.
Only one account has registry publishing access, which creates a thin publishing base. The organization-owned repository provides some backing, so this is a moderate rather than severe concern.
There have been no releases in the last five years, despite four releases over the package's lifetime. This is a meaningful sign of inactivity, though it does not by itself show the package is unusable.
There were no new or closed issues or pull requests in the last month, with one issue still open. This supports the broader picture of limited current maintenance.
Composer build tooling is present, but no security scanning tools were detected. The missing scanning is a hygiene gap, not evidence of a direct defect.
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.