Organization backing, tests, and a usable README provide a solid starting point. Composer lifecycle scripts and absent security scanning leave extra maintenance and review work.
57%
Total Score
75
75
50
Four Composer lifecycle scripts run during install, project creation, or updates. These may be normal for a Laravel starter kit, but they add install-time behavior that consumers must review and maintain.
The package is 473 days old with three releases, but there have been no releases in the last 12 months. Its earlier 22-day median interval shows an initial release cadence that has since stopped.
The repository recorded zero commits and zero active maintainers in the last three months, consistent with the registry's lack of releases in the last year. This materially raises abandonment risk.
The repository name matches the package, reducing the risk of an unrelated source repository, but the README does not mention the package name. That leaves a small transparency concern.
Composer is used as a build tool, providing basic project tooling, but no security scanning tools are configured. The missing scanning is a maintenance and transparency gap.
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 | — | — |
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.