A security policy is absent, and all three workflow actions are unpinned. Tests, a README, and release notes improve transparency, but the large application template increases upkeep demands.
43%
Total Score
50
50
92
50
The package declares 21 runtime dependencies and 7 development dependencies, making this a broad application template with considerable dependency upkeep exposure. No provided dependency signal establishes that the individual dependencies are unsafe.
The latest release was over five years ago, with no releases in the last 12 months and only three releases overall. This is substantial abandonment risk for a Laravel application template.
The repository recorded zero commits and zero active maintainers in the last three months, consistent with the long gap since the latest release. No provided signal shows current maintenance capacity.
There were no new or closed issues or pull requests in the last month, while two issues remain open. This adds limited evidence of an inactive project, though issue counts alone are not decisive.
The linked repository has no security policy. For a template containing authentication, teams, permissions, and other application infrastructure, this reduces transparency around vulnerability reporting and handling.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
laravel/tinker Version ^2.0 | — | — |
fideloper/proxy Version ^4.4 | — | — |
laravel/sanctum Version ^2.6 | — | — |
calebporzio/sushi Version ^2.1 | — | — |
guzzlehttp/guzzle Version ^7.0.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.