It includes tests, a changelog, a matching MIT license, and a security policy. The repository shows no commits in three months, while both workflow actions are unpinned; only two releases also limit maturity evidence.
62%
Total Score
50
88
88
The registry namespace and repository are owned by the same individual account. This is coherent ownership, but it does not provide organizational backing or a broader maintenance base.
Only two releases have been published, both within a few hours on the first release day, so there is limited evidence of sustained maintenance or release discipline.
The repository recorded zero commits and zero active maintainers over the last three months. For a package only about five months old, that is a meaningful warning about current maintenance capacity.
Composer build tooling is present, but no security-scanning tools were detected. This is a hygiene gap rather than evidence that the package is unsafe.
The single workflow was fully analyzed with no dangerous triggers, untrusted checkouts, script injection, or audit findings. However, both action references are unpinned, leaving avoidable build-integrity risk.
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 | — | — |
illuminate/support Version ^10.0|^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.