atoms/phpstan-rules

This is a young but currently healthy-looking development tool release. It has a clear MIT license, a complete 72-file source and artifact tree with extensive tests, frequent recent releases, active repository commits, organization backing, and no deprecation, archive status, install-time scripts, or dangerous workflows. The main reservations are its only 22 days of history, a two-contributor base with one contributor responsible for 85% of recent commits, no security policy or security scanning, and no changelog; these reduce maturity and transparency but do not outweigh the concrete maintenance and testing evidence.

Latest 0.6.0

Packagist

80%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

Eight releases in 22 days, with a median interval of about 1.5 days, show active early development. However, the very short history limits evidence of long-term maintenance stability.

Repo bus factor

One contributor made 85% of the 20 recent commits, creating concentration risk. The second contributor remains active and the repository is owned by an organization, which partly compensates for the individual bus factor.

Repo issue activity

There are no recent issues or pull requests, so there is little evidence of community support or issue handling. Because the README directs development to the monorepo, this is a limited concern rather than evidence of abandonment.

Repo popularity

The repository has zero stars, forks, and watchers. This is weak external validation, but popularity is only supporting evidence and the package is very new and organization-backed.

Repo tooling

Composer is used as a build tool, but no security scanning tools are detected. The missing scanning capability is a security-process gap, though it is not by itself evidence of unhealthy maintenance.