The project is not archived and provides tests, release notes, and a license. The package has had no registry release in more than seven years, while recent repository activity is absent and the repository does not identify this package in its README. All workflow actions are unpinned, adding maintenance and build-integrity concerns.
44%
Total Score
50
100
72
75
The package has 21 releases but none in the last seven years, and the latest registry release was published in January 2019. That long gap is strong evidence of abandonment risk for a dependency.
The repository recorded zero commits and zero active maintainers in the last three months. Combined with the stale registry release history, this materially increases abandonment risk.
The repository name does not match the package name and its README does not mention the package. That weakens confidence that the linked repository directly corresponds to this release, beyond an ordinary subpackage naming difference.
The repository uses Make and Composer for builds, but no security scanning tools were detected. The build setup is established, while the missing scanning is a modest transparency gap.
No security policy was found in the repository. For an OAuth server bundle handling authentication flows, the absence of a documented vulnerability-reporting path is a meaningful transparency gap.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
symfony/security-bundle Version ~3.0|~4.0 | — | — |
symfony/framework-bundle Version ~3.0|~4.0 | — | — |
friendsofsymfony/oauth2-php Version ~1.1 | — | — |
symfony/dependency-injection Version ~3.0|~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.