kmaking/multi-auth

Release historydanger

Only one release exists, published about eight years ago, with no releases in the last 12 months. This is strong evidence of an unmaintained release line.

Repo commit activitydanger

The repository recorded no commits and no active maintainers in the last three months, consistent with the release history showing prolonged inactivity.

Maintainerscaution

One registry maintainer is a thin publishing base, increasing continuity risk for an already inactive project. The linked repository is user-owned rather than organization-backed.

Repo toolingcaution

Composer build tooling is present, but no security scanning tooling was detected. That limits evidence of ongoing automated security checks.

Security policycaution

The repository has no security policy, leaving no documented process for reporting or handling security issues. This adds a transparency gap, though it does not by itself show a security defect.