Keycloak SSO Integration Bundle for Pimcore
68%
Total Score
50
100
83
90
The package has a substantial README and a changelog, and the repository uses GitHub Releases, which support usability and release transparency. Tests are absent from both the artifact and repository, leaving a maintenance and regression-validation gap.
The repository is owned by an individual user rather than an organization, so there is no visible organizational backing to offset the small maintainer base. This increases continuity risk, especially alongside absent recent commits.
The repository recorded zero commits and zero active maintainers in the last 3 months. Although recent registry publication and a same-day repository push partly compensate, the lack of recent development activity is a material abandonment and maintenance concern.
There are no open issues or pull requests and no issue or pull-request activity in the last month. This avoids an unresolved backlog but also provides little evidence of an engaged maintainer or user community.
The repository has only 1 star, 1 fork, and 1 watcher. Low popularity is supporting caution about external validation and bus-factor resilience, but it is not by itself evidence that the package is unsafe to depend on.
We didn't find any vulnerabilities for this package.
No maintainer information available.
| Dependency | Last Release | Score |
|---|---|---|
pimcore/pimcore Version ^11.0 || ^12.0 | — | — |
symfony/framework-bundle Version ^6.2 | — | — |
stevenmaguire/oauth2-keycloak Version ^2.0 | — | — |
knpuniversity/oauth2-client-bundle Version ^2.10 | — | — |
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.