Tests, a stable v1.0.2 release, and organization backing provide useful structure. However, the repository has had no commits since February, while all five workflow actions are unpinned and one workflow grants broad write access. The missing security policy and scanning further reduce transparency.
58%
Total Score
67
100
83
67
There were zero commits and zero active maintainers in the last three months, and the repository's last push was in February. For a starter kit, that is a meaningful maintenance and abandonment concern.
The package is young, with two releases over roughly eight months and a short median interval between them. This shows initial publishing activity but provides limited long-term release history.
The repository has three stars, one fork, and no watchers, indicating limited adoption evidence. Popularity is supporting evidence only, so this mildly reduces maturity confidence rather than deciding the result.
Composer build tooling is present, but no security scanning tools were detected. The missing scanning is a hygiene gap for a package intended to seed application projects.
The repository has no security policy, leaving reporting and response expectations undocumented.
We didn't find any vulnerabilities for this package.
No maintainer information available.
| Dependency | Last Release | Score |
|---|---|---|
laravel/tinker Version ^2.10.1 | — | — |
laravel/fortify Version ^1.30 | — | — |
laravel/framework Version ^12.0 | — | — |
laravel/wayfinder Version ^0.1.9 | — | — |
inertiajs/inertia-laravel 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.