The package is licensed, tested, documented, and has a recent GitHub release. Its organization-backed repository is active, but one contributor handles all recent commits and no security policy is present.
68%
Total Score
83
100
88
75
The package is only 102 days old and has two releases, with a 31-day median interval. This is limited maturity evidence, though both releases were published within the last 12 months.
All eight recent commits came from one contributor, creating concentration risk. Organization backing partly offsets this because maintenance can be handed off, but no second active contributor is shown.
Composer build tooling is present, but no security-scanning tool was detected. This is a modest transparency gap for a package with only a short release history.
The repository has no security policy, leaving vulnerability reporting and response expectations undocumented.
All five analyzed workflow action references are unpinned, so their exact revisions are not reproducibly fixed. One workflow also grants top-level write permissions, but there are no untrusted checkouts, script injections, or higher-confidence audit findings.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
illuminate/console Version ^11.0|^12.0|^13.0 | — | — |
illuminate/support Version ^11.0|^12.0|^13.0 | — | — |
illuminate/database Version ^11.0|^12.0|^13.0 | — | — |
illuminate/filesystem Version ^11.0|^12.0|^13.0 | — | — |
directorytree/opensearch-client Version ^1.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.