The package is licensed and has no install-time scripts, but documentation and repository security practices are thin. Its tiny artifact may be intentional, yet maintenance and repository identity remain weak.
38%
Total Score
0
69
75
This package has only one release, published about five years ago, with no releases in the last 12 months. That provides strong evidence of abandonment risk for a dependency expected to receive maintenance.
The repository recorded zero commits and zero active maintainers in the last three months, consistent with the long release gap and providing no evidence of current maintenance capacity.
The artifact has no README, tests, or changelog. The missing tests and changelog are normal for published artifacts, but the missing README reduces consumer transparency for a Composer package.
The repository name does not match the package name, and no README mention was available. This raises concern that the linked repository may not clearly belong to the published package.
Composer is used as the build tool, which fits the ecosystem, but no security scanning tooling was detected. That is a supporting hygiene gap rather than evidence of unsafe behavior by itself.
We didn't find any vulnerabilities for this package.
No maintainer information available.
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.