It has no repository security policy or automated security scanning, and its popularity is minimal. Tests, a README, and an organization-owned repository provide useful support, but the release is still a risky long-term dependency.
48%
Total Score
50
67
50
The package has had no release in over three years and none in the last 12 months, despite five releases overall. This is strong evidence of abandonment risk for a project template.
The repository recorded zero commits and zero active maintainers in the last three months, consistent with the prolonged release gap. No provided signal shows ongoing maintenance capacity.
The package defines post-autoload-dump and post-update-cmd scripts, so installation or updates execute project commands. This deserves some attention, but the signal alone does not show unsafe behavior.
The repository has one star, zero forks, and one watcher, so there is little visible community support or outside validation. Low popularity is supporting evidence rather than a verdict on its own.
The project uses Make and Composer, which supports a reproducible development workflow, but it has no reported security scanning tools. The tooling is therefore useful but incomplete for maintenance assurance.
We didn't find any vulnerabilities for this package.
No maintainer information available.
| Dependency | Last Release | Score |
|---|---|---|
laravel/tinker Version ^2.8 | — | — |
laravel/sanctum Version ^3.2 | — | — |
guzzlehttp/guzzle Version ^7.2 | — | — |
laravel/framework Version ^10.10 | — | — |
league/flysystem-aws-s3-v3 Version ^3.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.