MIT licensing, a substantial README, and repository tests provide useful transparency. The package's repository does not identify it, and the project shows no recent maintenance, so pinning this fork carries abandonment risk.
58%
Total Score
50
75
75
The package is about 14 months old with 41 releases, but it has had no releases in the last 12 months. That sharply limits evidence of ongoing maintenance.
The repository recorded no commits and no active maintainers during the last 3 months. This is a meaningful abandonment concern despite the repository being unarchived.
The repository name does not match the package name and its README does not mention this package. Although forks can use different names, the lack of identification weakens provenance transparency.
Composer build tooling is present, but no security scanning tools were detected. The missing scanning is a modest hygiene gap rather than evidence that the release is unsafe.
The repository has no security policy. This is a transparency and response-process gap, though it is less significant than the lack of recent maintenance.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
ramsey/uuid Version ^4.0 | — | — |
onelogin/php-saml Version ^3.0|^4.0 | — | — |
illuminate/console Version ^8.0|^9.0|^10.0|^11.0|^12.0 | — | — |
illuminate/support Version ^8.0|^9.0|^10.0|^11.0|^12.0 | — | — |
illuminate/database Version ^8.0|^9.0|^10.0|^11.0|^12.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.