Usable with caveats: the package is licensed, documented, tested, and not deprecated or archived, but it has only two releases and no commits or active maintainers in the last three months. Zero repository adoption and missing security controls add uncertainty for a payment integration.
58%
Total Score
33
100
83
80
The repository recorded zero commits and zero active maintainers during the last three months. Combined with only two releases, this is the strongest maintenance concern and raises the risk of slow fixes.
The repository owner is a user account rather than an organization, and the registry has one publishing maintainer. This provides limited visible institutional backing for ongoing support.
The package is young at 241 days and has only two releases, with roughly 143 days between them. That limited history provides little evidence of long-term maintenance capacity.
There is one open issue and no issue or pull-request activity in the last month. This is limited evidence of community support, though it is not by itself proof of abandonment.
The repository has zero stars, forks, and watchers. Popularity is not required for health, but the absence of any visible adoption removes useful supporting evidence for this payment package.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
illuminate/http Version ^10.0|^11.0|^12.0|^13.0 | — | — |
guzzlehttp/guzzle Version ^7.0 | — | — |
illuminate/support Version ^10.0|^11.0|^12.0|^13.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.