The package has a usable README and tests in the published artifact, and its organization-owned repository is not archived. It has no security policy or scanning, leaving limited evidence of ongoing upkeep.
45%
Total Score
50
75
75
The package is over eight years old, with no releases in the last 12 months and only one recorded release date. That strongly raises abandonment risk for a dependency tied to an external authentication service.
The repository recorded zero commits and zero active maintainers in the last three months. Together with the old release history, this indicates maintenance has effectively stalled.
The repository has zero stars, one fork, and one watcher, so there is little community visibility to compensate for the thin maintenance evidence. Popularity is supporting evidence rather than a verdict on its own.
Composer build tooling is present, but no security scanning tools were detected. That limits evidence of automated security upkeep, although it is not by itself proof of unsafe code.
The linked repository has no security policy, reducing transparency about how vulnerabilities should be reported and handled. This is a secondary concern behind the clear maintenance slowdown.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
illuminate/contracts Version ^5.1 | — | — |
league/oauth2-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.