The README provides little practical guidance, and the repository has no security policy or scanning tools. MIT licensing, organization ownership, a matching repository, and no install scripts provide useful safeguards.
58%
Total Score
75
79
75
A README is present, but its installation and usage sections say “soon,” leaving consumers without meaningful integration guidance. Missing tests and a changelog are normal for the published artifact and are not counted against it.
The latest release was over three years ago, with no releases in the last 12 months; the eight-release history shows a maintained package that is now inactive.
The repository recorded zero commits and zero active maintainers in the last three months, consistent with the long release gap and raising abandonment risk.
Composer is used for the build, but no security scanning tools are configured, leaving one less layer of maintenance and dependency oversight.
The repository has no security policy, reducing transparency for reporting and handling vulnerabilities; this is a hygiene gap rather than evidence of an unsafe release.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
phpunit/phpunit Version ^9.0 | — | — |
laravel/framework Version ^9.0 | — | — |
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.