The package has a clear README, tests, and matching MIT licensing. Its small project footprint and absent security policy leave less evidence of ongoing maintenance, despite the repository remaining active rather than archived.
58%
Total Score
67
100
88
67
A post-autoload-dump script runs during Composer installation. This is a normal framework-package mechanism, but it gives installation behavior more execution surface than a package with no lifecycle scripts.
The registry lists one publishing account. Because the repository is user-owned and no broader organization backing is shown, the publishing base is thin, though registry access alone does not prove weak maintenance.
Only two releases were published, both within minutes on the same day, and there have been no releases in about 19 months. That makes ongoing maintenance uncertain for a package developers may depend on.
There were no commits and no active maintainers in the last three months, consistent with the long release gap and raising abandonment concern.
Composer build tooling is present, but no security scanning tool was detected. That is a transparency and hygiene gap rather than evidence that the release is unsafe.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
illuminate/support Version ^9.0|^10.0|^11.0|^12.0 | — | — |
illuminate/contracts Version ^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.