There are no repository tests or security scanning, and one person publishes the package. The MIT declaration, clear README, matching repository, and non-deprecated status are reassuring.
54%
Total Score
50
72
75
The package has four releases clustered over about four days, then no releases in the following 12 months. That weakens confidence in ongoing maintenance for a broad API integration package.
One registry publishing maintainer creates a thin operational base, with no organization backing shown to compensate for the concentration.
The release includes a substantial README, while the absence of tests and a changelog in the published artifact is normal packaging practice. The repository also reports no tests or changelog, which provides limited project documentation beyond the README.
The repository has 0 stars and 0 forks, with 1 watcher. Popularity is only supporting evidence, but these numbers provide little external evidence of maturity or review.
Composer build tooling is present, but no security scanning tools were detected. This is a meaningful transparency and maintenance gap for a package handling API credentials.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
illuminate/http Version ^11.0|^12.0 | — | — |
guzzlehttp/guzzle Version ^7.0 | — | — |
illuminate/support Version ^11.0|^12.0 | — | — |
illuminate/contracts Version ^11.0|^12.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.