The package is well documented, licensed, tested in its repository, and neither deprecated nor archived. One publisher and no commits in the last three months reduce maintenance confidence, while workflow issues add release-process risk.
64%
Total Score
67
100
75
One registry publishing account creates a thin operational base, so a departure or loss of access could affect release continuity. The matching repository owner provides direct project backing but is still a single-person effort.
The repository recorded zero commits and zero active maintainers in the last three months. The recent release shows the project has not vanished, but this still weakens confidence in ongoing maintenance.
No repository security policy was found, leaving contributors and users without a documented vulnerability-reporting path.
All 12 analyzed action references are unpinned, and one workflow has a high-confidence template-injection finding; one workflow also grants top-level write permissions. The audit completed fully and found no untrusted checkout or script-injection trigger, so these are workflow hygiene and release-process risks rather than an automatic adoption blocker.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
illuminate/support Version ^12.0 || ^13.0 | — | — |
illuminate/database Version ^12.0 || ^13.0 | — | — |
illuminate/contracts Version ^12.0 || ^13.0 | — | — |
thecodingmachine/safe Version ^3.3 | — | — |
spatie/laravel-package-tools Version ^1.92 | — | — |
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.