Package Health/narekmarkosyan/laravel-admin-telegram-two-factor

narekmarkosyan/laravel-admin-telegram-two-factor

This release appears usable and actively published, with a matching non-archived repository, recent release activity, an MIT license, no deprecation, no install-time lifecycle scripts, and a modest runtime dependency set. However, it remains an immature v0.0.5 package with only one active contributor, a single recent commit, no tests or changelog, no security policy or security scanning, and negligible repository adoption; those limitations are particularly relevant for an authentication-related dependency. The package is not evidently abandoned, but it should be adopted with review, testing, and a contingency plan for maintainer availability.

Latest v0.0.5

Packagist

62%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Maintainers

Only one account has registry publishing access. Because the repository is user-owned rather than organization-owned, this represents a genuine continuity limitation, though registry access alone does not establish maintenance activity.

Package scaffolding

A README is present, but neither the artifact nor repository contains tests or a changelog. For an authentication package, the lack of tests is a meaningful maintenance and verification gap.

Project backing

The repository is owned by an individual user rather than an organization, so there is no visible organizational backing to compensate for the concentrated maintainer base.

Repo bus factor

One contributor made 100% of the commits in the last three months. With user ownership and no organizational backing, the package has a high single-maintainer continuity risk.

Repo commit activity

Only one commit was recorded in the last three months by one active maintainer. Recent activity exists, but the very low volume indicates limited maintenance capacity.