The repository has basic project structure, tests, and clear licensing. Its maintenance and supply-chain posture are too weak for a new dependency, especially given the independent scan flag.
42%
Total Score
0
79
50
Only two releases exist, and none were published in the last 12 months; the latest release was about 16 months ago. This indicates a thin and currently inactive release history.
The repository recorded zero commits and zero active maintainers in the last three months, consistent with the long release gap and raising abandonment risk.
Composer build tooling is present, but no security-scanning tools were detected. That leaves an avoidable gap in ongoing project hygiene.
The repository has no security policy, reducing transparency for reporting and handling security issues. This is a meaningful gap for a package with an independent scan concern.
We didn't find any vulnerabilities for this package.
No maintainer information available.
| Dependency | Last Release | Score |
|---|---|---|
laravel/tinker Version ^2.9 | — | — |
laravel/framework Version ^11.0 | — | — |
yusologia/lara-core Version ^1.0 | — | — |
php-open-source-saver/jwt-auth Version ^2.3 | — | — |
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.