vivek-raghuvanshi/laravel-keycloak-guard

Release historydanger

This is the package's only release, published over three years ago, with no releases in the last 12 months. That long period without a new release is strong evidence of inactive maintenance for an authentication library.

Maintainerscaution

Only one registry account has publishing access, so there is little visible publishing redundancy. This is a modest concern, though the repository is user-owned and the registry list alone does not prove maintenance capacity.

Project backingcaution

The package and repository are both owned by the same user account, and no organization backing is shown. This supports clear ownership but offers limited evidence of broader maintenance capacity.

Repo toolingcaution

Composer build tooling is present, but no security-scanning tooling was detected. For an authentication package, that is a meaningful hygiene gap, though not evidence of a specific vulnerability.

Security policycaution

The repository has no security policy, leaving no documented channel or process for reporting vulnerabilities in an authentication-related package.