The package has clear documentation, a matching repository, tests, and an MIT license. Its small project footprint and lack of recent development or security policy make long-term maintenance less certain.
58%
Total Score
38
100
88
63
There were zero commits and zero active maintainers in the last three months, consistent with the latest push being over two years ago. This materially raises abandonment and compatibility risk.
A post-autoload-dump Composer lifecycle script runs during installation. This is an additional install-time execution surface, though the signal provides no evidence that it is unsafe.
Two registry publisher accounts are listed, and the repository is owned by the same individual. This is a small maintainer base, but it is consistent with the individual-owned project backing.
The repository and registry are both owned by the same individual rather than an organization. This is consistent ownership evidence, but it also means there is no visible organizational backing to offset the small maintainer base.
The package has six releases over roughly nine years, but none in the last 12 months and its latest release was over two years ago. This is meaningful maintenance risk despite the established release history.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
illuminate/support Version ^11.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.