A clear README, tests, MIT declaration, and matching repository make the project understandable to adopt. Its Composer install scripts add review overhead, while the lack of a security policy leaves maintenance practices less transparent.
47%
Total Score
0
71
50
The package has only two releases, both published about 841 days ago, with no releases in the last 12 months. This strongly suggests limited ongoing maintenance, despite the stable 1.0.1 version.
The repository recorded zero commits and zero active maintainers in the last three months, consistent with the package's long release gap. The repository is not archived, but current maintenance capacity is not demonstrated.
Composer install, create-project, and update lifecycle scripts are present. They may be normal for a Laravel application template, but they increase installation and update review overhead.
The repository has 0 stars, 0 forks, and 1 watcher. Popularity is only supporting evidence, but these values provide little evidence of community review or shared maintenance.
Composer is used as the build tool, which fits the package ecosystem. No security scanning tools are configured, leaving automated security hygiene un demonstrated.
We didn't find any vulnerabilities for this package.
No maintainer information available.
| Dependency | Last Release | Score |
|---|---|---|
laravel/tinker Version ^2.8 | — | — |
tymon/jwt-auth Version ^2.1 | — | — |
laravel/sanctum Version ^3.3 | — | — |
guzzlehttp/guzzle Version ^7.2 | — | — |
laravel/framework Version ^10.10 | — | — |
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.