The MIT license, tests, and repository release setup improve transparency. Install-time scripts and no security policy add friction, and this project should not be expected to receive ongoing fixes.
39%
Total Score
25
63
50
Only two releases were published, both in May 2022, with no releases in the last 12 months after roughly four years of package age. This is strong evidence of abandonment risk.
The repository recorded zero commits and zero active maintainers in the last three months, consistent with the long release gap and indicating no current maintenance capacity.
There were no new or closed issues or pull requests in the last month. While a small project can be quiet, this provides no evidence of ongoing maintenance alongside the absent commits and releases.
Composer build tooling is present, but no security scanning tools were detected. This is a moderate transparency and maintenance gap, though it does not outweigh the inactivity evidence.
The repository has no security policy, leaving no documented process for reporting or handling vulnerabilities. This matters for a Laravel application with runtime dependencies.
We didn't find any vulnerabilities for this package.
No maintainer information available.
| Dependency | Last Release | Score |
|---|---|---|
laravel/tinker Version ^2.5 | — | — |
laravel/sanctum Version ^2.11 | — | — |
guzzlehttp/guzzle Version ^7.0.1 | — | — |
laravel/framework Version ^8.65 | — | — |
darkaonline/l5-swagger Version ^8.3 | — | — |
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.