The release has a complete README, tests, changelog, matching MIT license, and an active-looking repository structure. It is maintained by one person, has no security policy, and uses an install-time script, leaving less operational transparency.
67%
Total Score
50
94
67
The package defines a post-autoload-dump install-time script. This may be normal Composer integration, but it adds execution during installation and modestly increases dependency risk.
Only one registry account has publish access. Because the project is user-owned rather than organization-backed, this indicates a thin publishing base, although it does not by itself prove abandonment.
This is a young package, about 137 days old, with only two releases and both published within the same day. That is limited evidence of sustained maintenance, though the package is still early in its lifecycle.
The repository recorded zero commits and zero active maintainers during the last three months. For a package this young, that is a meaningful sign that maintenance may have slowed.
No repository security policy was found. This is a transparency gap for reporting and handling vulnerabilities, though it is not severe enough to make the release unfit on its own.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
illuminate/cache Version ^10.0|^11.0|^12.0 | — | — |
guzzlehttp/guzzle Version ^7.8 | — | — |
illuminate/support Version ^10.0|^11.0|^12.0 | — | — |
guzzlehttp/promises Version ^2.2 | — | — |
illuminate/contracts Version ^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.