Healthy and suitable to use, with a few transparency and security-hygiene caveats. It has recent releases, active contributors, tests, release notes, and a matching source repository, but the artifact lacks a README and the repository has no security policy or security scanning.
76%
Total Score
100
100
89
63
Four install and update lifecycle scripts run package commands, increasing installation complexity and execution surface. This is a caution for supply-chain transparency, although lifecycle scripts can be normal for a Laravel starter kit.
The repository has one star and no forks or watchers, so there is little public adoption evidence. Popularity is only supporting evidence, and the active release and commit signals are stronger.
The repository uses Composer build tooling, but no security scanning tools were detected. This leaves a security-process gap, though the absence of scanning alone does not establish abandonment or unsafe code.
No security policy was found in the repository, reducing transparency about vulnerability reporting and maintenance response.
One of the two workflows lacks top-level token permissions, while the other declares read-only permissions and neither workflow requests top-level write access. This is a minor workflow-hygiene gap rather than a severe risk.
We didn't find any vulnerabilities for this package.
No maintainer information available.
| Dependency | Last Release | Score |
|---|---|---|
laravel/tinker Version ^3.0 | — | — |
laravel/fortify Version ^1.30 | — | — |
laravel/framework Version ^13.0 | — | — |
laravel/wayfinder Version ^0.1.9 | — | — |
spatie/laravel-data Version ^4.18 | — | — |
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.