The MIT license, included tests, and lack of install-time scripts make adoption straightforward. No security policy or automated security scanning is documented, and publishing depends on one maintainer.
78%
Total Score
67
100
94
75
Only one registry account has publishing access, which leaves a thin release-control base; the frequent release history provides some compensation but not full resilience.
The registry namespace and repository owner match an individual account rather than an organization, so the project has limited visible institutional backing.
Composer build tooling is present, but no security scanning tool is configured, leaving a modest transparency and maintenance gap.
The repository has no security policy, so the process for reporting and handling vulnerabilities is not documented.
No GitHub Actions workflows were found, so there are no workflow findings or unpinned actions, but automated repository checks are not evidenced.
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.