The repository has no security policy and its two workflow actions are unpinned. MIT licensing, release notes, an unarchived organization-owned repository, and repository tests help, but the package name is not mentioned there.
58%
Total Score
75
100
81
75
The package has 23 releases, but none in the last 12 months and its latest registry release was in December 2022. This indicates materially slowed delivery and raises maintenance risk.
The repository recorded zero commits and zero active maintainers in the last three months. That is a concrete sign of limited recent maintenance capacity.
The repository name does not match the package name and its README does not mention the package. Although this could reflect a fork or related bundle, the link should be verified because the source may not directly represent this package.
The project uses Make and Composer, showing basic build tooling, but no security-scanning tool was detected. The missing scanner is a hygiene concern rather than proof of unsafe code.
No repository security policy was found. For an OAuth server bundle, the absence of a documented vulnerability-reporting path reduces transparency around security maintenance.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
symfony/twig-bundle Version ^4.4 || ^5.1 | — | — |
symfony/security-bundle Version ^4.4 || ^5.1 | — | — |
symfony/framework-bundle Version ^4.4 || ^5.1 | — | — |
friendsofsymfony/oauth2-php Version ~1.1 | — | — |
symfony/dependency-injection Version ^4.4 || ^5.1 | — | — |
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.