The MIT declaration, tests, and Composer setup provide basic project structure. Several Composer lifecycle hooks run during installation, so inspect their behavior before adopting it.
38%
Total Score
0
64
50
The package has only one release, published about four years ago, with no releases in the last 12 months. That leaves compatibility and maintenance largely unproven.
There were no commits and no active maintainers in the last three months, while the repository was last pushed about four years ago. This is strong evidence that maintenance has stopped or is not observable.
The package declares four Composer lifecycle scripts, including post-autoload-dump and post-update-cmd. These are common in Laravel projects but increase installation and update behavior that should be understood.
The repository name matches the package, but its README does not mention the package name. This makes the package's relationship to the repository less clear, despite the matching repository name.
The repository has zero stars and forks and only one watcher. Popularity is not required for a healthy package, but these numbers provide no supporting evidence of adoption or community review.
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.75 | — | — |
fruitcake/laravel-cors Version ^2.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.