The source repository has no recent commits, and its release metadata conflicts with the assessed v4.1.3 version. Licensing, tests in the repository, and a readme are reassuring, but this looks unmaintained and is a poor new dependency choice.
30%
Total Score
0
71
50
The package has had no release in more than 7 years and none in the last 12 months. That long publication gap is strong evidence of abandonment for a library dependency.
The repository recorded zero commits and zero active maintainers in the last 3 months, consistent with a project that has been inactive for years. This materially raises abandonment risk.
The repository uses Composer, confirming basic build tooling, but it has no security scanning tools. That is a minor hygiene gap, not a substitute for the stronger inactivity evidence.
No repository security policy was found, leaving vulnerability reporting and response expectations undocumented. This adds a transparency gap for a package handling OAuth integrations.
The assessed release is v4.1.3, but the registry reports v2.0.23 as the latest version. This inconsistency weakens confidence in the release metadata and provenance.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
illuminate/http Version ~5.7.0|~5.8.0|~5.9.0 | — | — |
guzzlehttp/guzzle Version ~6.0 | — | — |
illuminate/support Version ~5.7.0|~5.8.0|~5.9.0 | — | — |
league/oauth1-client Version ~1.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.