The package has a clear MIT license, tests, a matching repository, and no install scripts. Its small ownership base and limited security process reduce resilience for long-term maintenance.
60%
Total Score
63
100
83
88
Only one registry account has publish access. That is a real continuity weakness for a user-owned project, because a single publisher creates a limited recovery and review base.
The registry namespace and repository belong to the same individual account. This confirms ownership alignment, but it does not provide organization-level backing.
The package has had no release in 667 days, with all six releases clustered near its initial publication. This is meaningful evidence of stalled maintenance despite the stable major version.
There were zero commits and zero active maintainers in the last three months. Combined with the old release history, this points to limited current development capacity.
The repository has two stars, zero forks, and one watcher. Low popularity provides little external validation, but popularity is supporting evidence rather than a health verdict.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
guzzlehttp/guzzle Version ^6.3|^7.0 | — | — |
illuminate/support Version ^6.0|^7.0|^8.0|^9.0|^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.