The MIT license, tests, matching repository, and clear README support straightforward use. Install-time scripts and the lack of security scanning add modest operational friction.
64%
Total Score
50
80
50
Four install and update lifecycle scripts run during Composer operations, increasing the amount of code executed automatically during installation, although this is common for Laravel project scaffolding.
The package has only two releases, both published in June 2025, and none in the following 12 months; this suggests maintenance may have stopped, though a small starter kit can be intentionally stable.
The repository recorded zero commits and zero active maintainers in the last three months, weakening evidence of ongoing maintenance after the initial release burst.
Composer is used as the build tool, but no security scanning tooling is present, leaving a modest transparency and maintenance-control gap.
The repository has no security policy, reducing clarity about how vulnerabilities should be reported and handled.
We didn't find any vulnerabilities for this package.
No maintainer information available.
| Dependency | Last Release | Score |
|---|---|---|
laravel/tinker Version ^2.10.1 | — | — |
laravel/framework Version ^12.0 | — | — |
laravel-json-api/laravel Version ^5.1 | — | — |
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.