The repository includes tests, documentation, and a matching source project, but maintenance has gone quiet and workflow dependencies are unpinned. The missing security policy is a smaller transparency gap.
62%
Total Score
50
100
88
67
The package and repository are owned by the same individual account, so the source ownership is consistent. Individual ownership provides less organizational continuity than a backed project, but no mismatch is shown.
The package has 10 releases over roughly 11 years, but none in the last 12 months and the latest release was in March 2023. This is meaningful evidence of a long release gap, despite its established history.
There were zero commits and zero active maintainers in the last three months. Combined with the old latest release, this indicates currently quiet maintenance.
The repository uses Composer for builds, but no security scanning tools were detected. The absent scanning is a modest process gap rather than evidence of unsafe code.
The repository has no security policy. This weakens transparency around vulnerability reporting, though it is not by itself evidence that the package is unsafe.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
illuminate/support Version ^10.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.