A single registry maintainer and no published security policy leave little visible support for long-term maintenance. The package does provide a clear README, tests, and licensing, which helps adoption but does not offset the inactivity.
40%
Total Score
25
83
83
The package has only two releases, with none in the last 12 months; its latest release was over four years ago. This is strong evidence of abandonment risk for a dependency that may need compatibility updates.
The repository recorded zero commits and zero active maintainers in the last three months, consistent with the release history showing no recent releases. The lack of observed maintenance materially lowers confidence in future support.
Only one account has registry publishing access, and the project is backed by a user-owned repository rather than an organization. This creates a thin visible support base, though registry access alone does not prove inactivity.
The repository has no security policy, leaving no documented process for reporting or handling vulnerabilities. This is a transparency and maintenance gap, not evidence that the package is unsafe.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
guzzlehttp/guzzle Version ^7.4 | — | — |
illuminate/support Version ^9.0 | — | — |
illuminate/notifications Version ^9.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.