Frequent recent releases, a stable major version, and thorough usage documentation support adoption. The small project has no security policy or scanning, while recent repository activity is absent, limiting maintenance assurance.
68%
Total Score
50
89
75
The repository is owned by an individual account rather than an organization, so there is no organizational backing shown by this signal. That is not inherently unhealthy, but it provides no additional continuity assurance.
The repository recorded zero commits and zero active maintainers during the past three months. Combined with the absence of recent issue or pull-request activity, this weakens evidence of ongoing maintenance.
The repository has zero stars and forks and one watcher. Popularity is only supporting evidence, but these numbers provide little external evidence of review, adoption, or a broader contributor community.
Composer is used for the build, which fits the package ecosystem, but no security scanning tools are configured. The missing scanning reduces automated oversight without making the release unfit on its own.
The repository has no security policy. For a Laravel package used in applications, this limits transparency about vulnerability reporting and response procedures.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
symfony/finder Version >=5.4 | — | — |
illuminate/support Version >=8.0 | — | — |
illuminate/database Version >=8.0 | — | — |
illuminate/contracts Version >=8.0 | — | — |
illuminate/translation Version >=8.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.