Clear licensing, documentation, and release notes make integration easier. CI has security scanning and the package keeps a small runtime dependency surface.
68%
Total Score
83
100
100
50
A post-autoload-dump install script runs during Composer installation. This is a meaningful execution point for consumers, though the signal does not show that the script is harmful.
All 12 commits in the last 3 months came from one contributor. Organization backing provides some handoff capacity, but no second active contributor is shown, leaving a real continuity concern.
The repository has no security policy file. That weakens vulnerability-reporting transparency for a package involved in authentication and Shiny app integration.
All 12 analyzed action references are unpinned, which weakens build reproducibility and increases dependency-drift risk. The audit also found a high-confidence bot-condition issue, but no untrusted checkout or script injection was detected, so it does not independently make the release unsafe.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
illuminate/contracts Version ^11.0||^12.0||^13.0 | — | — |
spatie/laravel-package-tools Version ^1.16 | — | — |
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.