Package Health/nguyenanhung/telegram-messenger

nguyenanhung/telegram-messenger

There is no security policy or automated security scanning, and all three workflow actions are unpinned. The recent release and clear package documentation provide useful transparency, but the project has no recorded commits in the past three months.

Latest v2.0.7

Packagist

58%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Maintainers

Only one registry account can publish the package. The linked repository is owned by the same individual, so this reflects a genuinely thin maintainer base rather than normal organization publishing hygiene.

Project backing

The package and repository are both owned by the same individual account, confirming clear ownership but no organizational backing to provide maintainer redundancy.

Repo commit activity

The repository recorded zero commits and zero active maintainers in the past three months. Although the recent release and push show current publishing, the lack of development activity raises maintenance risk.

Repo issue activity

There are no open issues or pull requests and no issue or pull-request activity in the past month. This is neutral for a small package but provides little evidence of an active user or contributor community.

Repo popularity

The repository has only 3 stars and 2 forks. This is weak supporting evidence for maturity, though popularity alone does not determine whether a small package is healthy.