Documentation is thorough, and the source includes tests and a clear package layout. The unusually compressed release history and lack of recent commits make future maintenance less certain; workflow references are also unpinned.
62%
Total Score
50
100
88
67
The repository is owned by an individual account rather than an organization. That does not establish poor health, but it provides less visible institutional backing for a project already showing inactivity.
The package has 62 releases, all apparently published on January 29, with no later release across roughly eight months. That concentrated burst followed by a long gap raises maintenance uncertainty.
The repository recorded zero commits and zero active maintainers during the last three months. Combined with the long gap since the January release burst, this is a meaningful maintenance concern.
The repository uses Composer for builds, but no security scanning tools were detected. The missing scanning is a modest transparency gap rather than evidence of abandonment.
No security policy was found in the repository. This weakens vulnerability-reporting transparency, although it is a smaller concern than the inactive commit history.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
illuminate/support Version ^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.