Package Health/bpa/notifications-mattermost

bpa/notifications-mattermost

The stable major version and small dependency set limit integration risk. However, the project has not been released or committed to since February 2019, and its tiny repository offers little documentation or testing support.

Latest v1.1

Packagist

40%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

Only two releases were published, both in February 2019, with no releases in the last 12 months. This long release gap is strong evidence of abandonment risk.

Repo commit activity

There were zero commits and zero active maintainers in the last three months, consistent with the last repository push being in 2019. This is the clearest maintenance and abandonment concern.

Package file tree

The package and repository each contain only composer.json and two source files. This compact structure may fit a small notification handler, but it provides little visible project support beyond the implementation itself.

Package scaffolding

The artifact has no README, tests, or changelog, while the repository also has no tests or changelog. The GitHub release record is a small positive, but the missing consumer documentation and validation reduce transparency.

Project backing

The package and repository are tied to the same individual owner rather than an organization. That is valid project backing, but it provides no visible organizational redundancy if the sole maintainer stops work.