Package Health/andreybrigunet/flarum-ext-auth-easy4live

andreybrigunet/flarum-ext-auth-easy4live

This is a usable but lightly supported dependency with a clear MIT license, a matching source repository, a small and understandable dependency profile, and no deprecation or archive status. However, it has only one registry maintainer, no tests or changelog, no security policy or security scanning, no repository commits in the last 3 months, and negligible repository adoption; its 0.x version also indicates limited maturity. The recent release shows the package is not plainly abandoned, but the limited maintenance evidence and transparency gaps warrant caution before relying on it for a critical integration.

Latest v0.1.10

Packagist

62%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Maintainers

Only one account has registry publish access. This is a thin maintainer base and creates continuity risk, although registry access alone does not establish who actively maintains the project.

Package scaffolding

A README is present and GitHub Releases are used, but the artifact and repository contain no tests or changelog. For a small extension this is a genuine maintenance and transparency gap, though not by itself severe.

Project backing

The source repository is owned by an individual user rather than an organization, providing limited visible institutional backing. This is a continuity concern when combined with the single registry maintainer and absent recent commits.

Repo commit activity

The repository recorded zero commits and zero active maintainers in the last 3 months. Despite the recent push and recent release, this weakens evidence of sustained maintenance and raises abandonment risk.

Repo issue activity

There are no open issues or pull requests and no issue or pull-request activity in the last month. This is not inherently negative for a small extension, but it provides no evidence of an active user or contributor community.