pragmarx/google2fa-qrcode

Maintainerscaution

Only one account has registry publish access, leaving a thin publishing base. This is a modest resilience concern for a user-owned project, although recent releases provide some compensation.

Project backingcaution

The repository is owned by an individual account rather than an organization, so the single registry maintainer represents a real continuity limitation rather than ordinary organization publishing hygiene.

Repo commit activitycaution

The repository recorded no commits and no active maintainers in the last three months. The release on the latest push date partly offsets this, but the short-term activity gap remains a maintenance caution.

Repo toolingcaution

Composer build tooling is present, but no security-scanning tool was detected. For a package handling two-factor-authentication QR-code functionality, the missing automated security scanning is a meaningful hygiene gap.

Security policycaution

The repository has no security policy. That weakens the documented path for reporting vulnerabilities, although it does not show that the package is unsafe.