Healthy and suitable to depend on, with active releases, thorough tests and documentation, and a current source repository. Review the lack of a security policy and undeclared workflow token permissions before adopting it in a security-sensitive project.
86%
Total Score
80
100
94
75
Only one registry publishing account is listed, which limits publishing redundancy, but the linked repository has two active contributors and is user-owned rather than organization-backed.
Two contributors were active recently, with the leading contributor responsible for 75% of commits; this is some concentration but not a single-contributor project.
Composer build tooling is present, but no security scanning tools were detected, leaving automated vulnerability monitoring unconfirmed.
The repository has no SECURITY.md or other detected security policy, so the process for reporting and handling vulnerabilities is not documented.
The only workflow does not declare top-level token permissions. No write permissions were observed, but explicitly restricting permissions would provide stronger workflow hygiene.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
nesbot/carbon Version ^2.67|^3.0 | — | — |
illuminate/http Version ^10.0|^11.0|^12.0|^13.0 | — | — |
illuminate/cache Version ^10.0|^11.0|^12.0|^13.0 | — | — |
guzzlehttp/guzzle Version ^7.0 | — | — |
illuminate/console 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.