Connect your Laravel project to our centralized authentication service
62%
Total Score
caution
Usable with caveats: maintenance has recently slowed and the release workflow has risky credential and dependency-pinning practices.
The package has 37 releases over about four years, but only one release in the last 12 months. The recent v4.0.0 release provides some evidence of ongoing maintenance, but the low recent cadence remains a concern.
The repository recorded zero commits and zero active maintainers in the last three months. Although a recent release was pushed, this is still a meaningful maintenance-capacity concern.
Composer is used for the build, but no security-scanning tools were detected. The missing scanning automation is a transparency and hygiene gap rather than evidence of an unsafe release.
The repository has no security policy, leaving vulnerability reporting and response expectations undocumented.
All three analyzed action references are unpinned, and the high-confidence audit found an app token inheriting blanket installation permissions; the workflow also uses trusted publishing. These increase release-workflow exposure, though no untrusted checkout or script injection was found.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
illuminate/contracts Version ^12.0 | — | — |
spatie/laravel-package-tools Version ^1.9.2 | — | — |
henrotaym/laravel-flare-exception-handler Version ^4.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.