jiemo/phing-notify

The six-file project has no tests or security policy, and its repository does not mention the package. MIT licensing and no install-time scripts reduce avoidable concerns, but there is little evidence of ongoing care.

Latest 2.2

Packagist

38%

Total Score

Maintainer Stability

Maturity

Supply Chain

Health Score Breakdown

Release history

The last release was in April 2017, and there were no releases in the past 12 months. This roughly nine-year gap is strong evidence of abandonment risk despite four historical releases.

Repo commit activity

There were no commits and no active maintainers in the past three months, consistent with the last repository push occurring about nine years ago. This is substantial abandonment evidence.

Repo package mention

The repository name does not match the package name and its README does not mention the package. This creates caution that the linked source may not clearly document ownership of this release.

Repo popularity

The repository has zero stars and forks and only two watchers. Low popularity is supporting evidence rather than a verdict, but it offers no compensating community signal for the lack of maintenance.

Repo tooling

Composer and Phing are used for the build, showing basic project tooling. No security-scanning tool was detected, leaving a modest maintenance and assurance gap.