The repository has little visible adoption, and it lacks both a security policy and automated security scanning. Regular registry releases and an active, organization-backed repository provide useful continuity.
62%
Total Score
75
88
75
There were no commits and no active maintainers in the last three months. That weakens evidence of ongoing maintenance, even though the registry shows a recent release.
The repository has only 2 stars, 1 fork, and no watchers. Low adoption is supporting caution about project maturity, although popularity alone is not a health verdict.
Composer is used as a build tool, which is appropriate for this package, but no security scanning tools were found. That leaves a meaningful supply-chain transparency gap.
The repository has no security policy. Consumers therefore have no documented project channel or process for reporting security issues.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
filp/whoops Version ^2.1 | — | — |
cocur/slugify Version ^3.1 | — | — |
predis/predis Version ~1.1.0 | — | — |
google/recaptcha Version ^1.1 | — | — |
jenssegers/agent Version ^2.5.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.