Tests, release notes, a security policy, and dependency scanning provide useful project structure. Pinning the two workflow actions and establishing a longer maintenance record would make future updates easier to trust.
67%
Total Score
50
93
83
The package is 0 days old with only 2 releases, spaced about 12 hours apart, so there is not yet enough history to demonstrate sustained maintenance.
The repository records 0 commits and 0 active maintainers over the last 3 months; the package's age explains this, but it still leaves maintenance capacity unproven.
The single workflow was fully analyzed, uses read-only permissions, and has no audit findings, but both of its 2 action references are unpinned, leaving them exposed to upstream tag changes.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
illuminate/http Version ^10.0 || ^11.0 || ^12.0 || ^13.0 | — | — |
guzzlehttp/guzzle Version ^7.0 || ^8.0 | — | — |
illuminate/support Version ^10.0 || ^11.0 || ^12.0 || ^13.0 | — | — |
illuminate/container Version ^10.0 || ^11.0 || ^12.0 || ^13.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.