The package is licensed, documented, tested, and has a small runtime dependency surface. Its missing security policy leaves less guidance for handling vulnerabilities.
61%
Total Score
75
100
88
75
The package has 32 releases with a median interval of about 9 days, but it has had no release in the last 12 months and the latest release was about 20 months ago. That suggests maintenance may have slowed substantially.
The repository had zero commits and zero active maintainers in the last three months. Combined with the stale release history, this is evidence of weak current maintenance.
Composer build tooling is present, but no security-scanning tooling was detected. The missing scanner is a modest hygiene gap rather than evidence that the package is unsafe.
The repository has no security policy, so vulnerability-reporting and response expectations are not documented. The clear license and repository presence compensate for transparency in other areas, but not this operational gap.
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.