Recent commit activity is absent despite a recent release, and the repository has no security policy or scanning tool. Clear licensing, tests, release notes, and a matching repository provide useful transparency.
72%
Total Score
50
100
88
75
There were no commits and no active maintainers in the three months before collection, although one pull request was merged in the last month. This is a meaningful maintenance concern, especially alongside the single-maintainer structure.
The repository has one star, zero forks, and one watcher. This indicates limited adoption, but popularity is supporting evidence and does not outweigh the recent release history and available tests.
Composer build tooling is present, but no security scanning tools were detected. That is a modest transparency and maintenance gap rather than evidence of unsafe behavior.
The repository has no security policy. For a Laravel library, this leaves vulnerability-reporting expectations unclear and lowers transparency.
The single workflow was fully analyzed with no audit findings or untrusted-trigger sinks. Its one action is unpinned, which is a minor reproducibility and supply-chain hygiene concern.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
illuminate/support Version ^13 | — | — |
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.