Its MIT license, readable documentation, and simple dependency set improve transparency. A single maintainer and no security policy leave little evidence of ongoing support.
42%
Total Score
50
100
81
50
The latest release was published about nine years ago, with no releases in the last 12 months. This is strong evidence of abandonment for a package intended to track an external API.
The package has one registry maintainer, so ongoing support depends on a single person. That is a meaningful resilience concern for an unmaintained-looking project, although the linked repository is owned by the same user.
The repository recorded zero commits and zero active maintainers over the last three months, consistent with the long release gap. The repository is not archived, but there is no observed recent maintenance.
Composer build tooling is present, which supports reproducible package structure, but no security scanning tools were detected. The missing scanning is a modest hygiene gap alongside the broader maintenance concern.
The repository has no security policy. For a small API wrapper this is a transparency gap rather than a severe risk, but it gives consumers no documented route for reporting security issues.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
illuminate/support Version ~5.1 | — | — |
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.