The package is well documented, licensed, and has a small dependency surface. Its repository has had no commits in the last three months and has no security policy, making future upkeep less certain.
67%
Total Score
75
100
88
50
The repository recorded zero commits and zero active maintainers in the last three months. This is a meaningful maintenance concern, although the recent release history shows earlier activity.
Composer build tooling is present, but no security-scanning tooling was detected. The missing scanning layer is a modest transparency and maintenance gap.
The repository has no security policy. For examples and configuration templates this is less severe than for a runtime security library, but it still leaves vulnerability-reporting expectations unclear.
Version 0.13.0 is not a stable-major release, but it is not marked prerelease and recent releases contain no prerelease versions. The major-version status calls for some API-change caution rather than indicating abandonment.
No GitHub Actions workflows were present, so there are no workflow permission, trigger, or pinning risks to assess. This also means there is no observed repository automation supporting ongoing checks.
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.