stezkoy/flarum-telegram-notify

Maintainerscaution

Only one registry account has publish access. This is consistent with the repository being user-owned, but it leaves little publishing redundancy if that maintainer becomes unavailable.

Package scaffoldingcaution

A substantive README is present and GitHub Releases are used, but neither the artifact nor repository contains tests or a changelog; for an extension handling notifications, the missing tests are a maintenance and regression concern.

Project backingcaution

The repository owner is a user account, not an organization, so the single-maintainer concerns are not offset by explicit organizational backing.

Release historycaution

Nine releases in 16 days show active early development, but the very short package history provides little evidence of long-term maintenance or maturity.

Repo bus factorcaution

All 36 recent commits came from one contributor, with a 100% top-contributor share. Because the repository is user-owned rather than organization-owned, there is no provided project-backing evidence to compensate for this concentration.