Its MIT license, focused dependency set, and matching source repository make the package straightforward to inspect. The long period without releases or commits leaves maintenance and compatibility risks, while the lack of tests and a security policy reduces confidence in future changes.
42%
Total Score
25
75
50
The package has made no releases in roughly 8 years, with its latest release in October 2017; this is strong evidence of abandonment for a dependency expected to receive maintenance.
The repository recorded zero commits and zero active maintainers in the last 3 months, consistent with the package's long release gap and leaving compatibility issues unlikely to be addressed.
Registry publishing access is held by one maintainer. The linked repository is user-owned rather than organization-backed, so there is little visible redundancy if that maintainer stops supporting the package.
Composer build tooling is present, but no security scanning tooling is reported. This is a modest transparency and maintenance gap rather than evidence that the release is unsafe.
The repository has no security policy, leaving no documented process for reporting or handling vulnerabilities in a package that sends messages through provider APIs.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
illuminate/support Version ~5 | — | — |
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.