Package Health/pragmarx/google2fa-laravel

pragmarx/google2fa-laravel

Healthy and reasonable to depend on, with a few maintenance and transparency caveats. It has a long release history, current commits from two contributors, tests, documentation, and no deprecation or risky workflow findings; the missing security policy and inactive issue queue reduce confidence.

Latest v3.0.1

Packagist

78%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Project backing

The source repository is owned by an individual rather than an organization, so maintenance depends more directly on that person. This is partly offset by recent activity from two contributors and the package's established history.

Repo issue activity

The repository has 57 open issues and no issues or pull requests were closed or merged in the last month. This suggests that issue maintenance may be slow and is a real, though not severe, adoption caveat.

Repo tooling

Composer build tooling is present, but no security scanning tools were detected. The missing scanning coverage lowers transparency around automated security checks.

Security policy

No repository security policy was found. For an authentication package, the lack of a documented vulnerability-reporting process is a meaningful transparency gap.

Token permissions

The repository workflow does not declare top-level token permissions. Although no write permissions were detected, explicit least-privilege declarations would provide stronger CI security hygiene.