Expect limited resilience if the current maintainer becomes unavailable. The young project has useful tests, release notes, dependency scanning, and organizational backing, but workflow references are not pinned and install scripts need care.
68%
Total Score
67
50
94
50
Seven runtime dependencies and 18 development dependencies are a substantial but plausible profile for a Laravel starter application. The dependency surface adds update and compatibility exposure without indicating an abnormal design by itself.
Four install and update lifecycle scripts run automatically, including post-autoload-dump and post-update-cmd. This is normal for a Laravel starter application but increases the amount of package code executed during setup and updates.
The package is only 33 days old with five releases, all within the last 12 months. Releases are frequent, with a median interval of about 48 minutes, showing active initial iteration but little long-term maintenance history.
One contributor holds 100% of the 14 commits in the last three months. Organizational ownership provides some handoff potential, but no second active contributor is shown.
The repository recorded 14 commits in the last three months, so it is not dormant. All activity comes from one active maintainer, which limits evidence of durable maintenance capacity.
We didn't find any vulnerabilities for this package.
No maintainer information available.
| Dependency | Last Release | Score |
|---|---|---|
laravel/chisel Version ^0.1.1 | — | — |
laravel/tinker Version ^3.0.2 | — | — |
laravel/fortify Version ^1.37.3 | — | — |
laravel/framework Version ^13.23.0 | — | — |
laravel/wayfinder Version ^0.1.20 | — | — |
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.