Clear documentation, tests, licensing, and a recent release support integration. The single maintainer and no commits during the last three months make longer-term support less certain.
68%
Total Score
50
100
94
83
Only one registry publishing account is listed, leaving limited observable publishing redundancy. The long release history partly offsets this, but it remains a support continuity concern.
The package and repository are owned by the same individual account, so the single-maintainer observation reflects the project backing rather than a normal organization publishing setup.
The repository recorded no commits and no active maintainers during the last three months. Although a release was published recently, the lack of source activity lowers confidence in ongoing maintenance.
Only three issues are open and no pull requests are pending, so there is no large visible backlog. There was no issue or pull-request activity during the last month, which is consistent with the maintenance concern.
Composer build tooling is present, but no security scanning tools were detected. This is a modest transparency and maintenance-hygiene gap rather than evidence of unsafe code.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
psr/log Version >=1.0 | — | — |
psr/cache Version >=1.0 | — | — |
psr/simple-cache Version >=1.0 | — | — |
laravel/framework Version >=6.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.