The repository includes tests, a README, and a release note, but the package has not had a registry release since April 2023. Its declared MIT license conflicts with the repository's AGPL-3.0 license, and install-time scripts increase integration risk.
48%
Total Score
50
75
50
This package has only one release, published about three years ago, with none in the last 12 months. That is strong evidence of limited release maintenance for a package intended to be adopted as a dependency.
The manifest declares MIT, but the repository license file is recognized as AGPL-3.0. This unresolved mismatch creates material legal and adoption uncertainty.
The package defines four install- or update-time Composer lifecycle scripts, so installation can execute project code automatically. This is common for Laravel applications but still increases the operational burden of depending on the package.
The repository recorded zero commits and zero active maintainers in the last three months. Although it was pushed in January 2025, current development activity is not demonstrated.
The linked repository has no security policy. For an application handling authentication, Stripe payments, and customer data, that leaves vulnerability-reporting and response expectations unclear.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
laravel/tinker Version ^2.7 | — | — |
laravel/cashier Version ^14.7 | — | — |
laravel/sanctum Version ^3.0 | — | — |
tightenco/ziggy Version ^1.0 | — | — |
guzzlehttp/guzzle Version ^7.2 | — | — |
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.