pviojo/oauth2-keycloak

Clear documentation, tests, and a matching repository make the package easy to inspect. Its dependency set is small and the code is licensed, but the available maintenance and security-process evidence is limited.

Latest 2.0.2

Packagist

38%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

The package has had no release in nearly nine years: all five releases were published in October 2017, with none in the last 12 months. This is strong evidence of abandonment for a dependency that may need compatibility updates.

Repo commit activity

The repository recorded zero commits and zero active maintainers in the last three months, consistent with the release history showing no activity since October 2017.

Repo tooling

Composer build tooling is present, but no security-scanning tools were detected. That limits automated assurance for a security-sensitive integration.

Security policy

The repository has no security policy, leaving vulnerability reporting and response expectations undocumented. This is a transparency gap, particularly for an OAuth provider, although it is less severe than the inactivity evidence.