The MIT license and README provide basic transparency for consumers. There is no security policy or repository security scanning, leaving weaker protection around a package handling OAuth2 authentication.
38%
Total Score
0
69
83
This is the package's only release, published about 7 years ago, with no releases in the last 12 months. That strongly suggests abandonment and leaves no newer release to address compatibility or security issues.
The repository recorded no commits and no active maintainers in the last 3 months, consistent with the package's last update being about 7 years ago. This is a substantial maintenance and abandonment concern.
The repository has 1 star, 0 forks, and 1 watcher. Popularity is only supporting evidence, but these very low figures provide no meaningful external adoption signal to offset the lack of maintenance.
The repository uses Composer, but it has no security-scanning tools. For an OAuth2 authentication package, the absence of automated security checks is a meaningful hygiene gap.
No security policy is present in the repository. For a package handling authentication tokens, this reduces transparency about how vulnerabilities should be reported and handled.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
illuminate/auth Version ~5.3 | — | — |
illuminate/http Version ~5.3 | — | — |
firebase/php-jwt Version ~3.0|~4.0 | — | — |
guzzlehttp/guzzle Version ~6.0 | — | — |
illuminate/console Version ~5.3 | — | — |
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.