muhsamsul/yii2-alert

Basic documentation and a clean dependency and install profile reduce day-to-day integration risk. The small, single-owner project offers little security or adoption evidence, so future fixes and compatibility work are uncertain.

Latest v1.0.0

Packagist

38%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

The package has only one release, published about 10 years ago, with no releases in the last 12 months. This is strong evidence of abandonment risk for a dependency.

Maintainers

The registry lists one maintainer account, which is consistent with a personal project but leaves a thin publishing base if that maintainer becomes unavailable.

Package file tree

The package contains only three files, including its implementation, README, and Composer manifest. This is transparent and easy to inspect, though it also reflects a very small project with little supporting material.

Repo popularity

The repository has zero stars and forks and only one watcher. Popularity is not required for health, but these values provide no supporting evidence of community adoption or review.

Repo tooling

Composer is used as the build tool, which fits the package ecosystem, but no security scanning tooling is present. The missing scanning is a modest transparency and maintenance gap.