Documentation is present, but the very small source tree has no tests or security process. The package has had no release or commit activity for about 10 years, and its licensing is unresolved.
35%
Total Score
0
100
71
83
The package has made only two releases, both around its first publication, with no releases in the last 12 months. Its latest release is about 10 years old, which is strong evidence of abandonment risk.
The repository recorded zero commits and zero active maintainers over the last three months, consistent with the roughly 10-year gap since its last release. The linked repository is correctly identified, so this inactivity is meaningful.
Neither the package nor the linked repository declares or contains a recognized license. That leaves developers without clear permission to use, modify, or redistribute the code.
Composer is used for the build, but no security scanning tools are present. This is a modest hygiene concern and does not by itself establish that the release is unsafe.
The repository has no security policy. For an old OAuth-related integration package, the absence of a documented vulnerability-reporting path reduces transparency, though it is less significant than the maintenance gap.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
lucadegasperi/oauth2-server-laravel Version ~4.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.