Package Health/distortedfusion/php-cs-fixer-config

distortedfusion/php-cs-fixer-config

This is a small, focused development-tool configuration package with a clear README, matching repository, MIT licensing, stable releases, no deprecation, no install-time scripts, and organization backing. The latest release and repository push are current, but the repository shows no commits or active maintainers in the last three months, has very low adoption, no tests or changelog, lacks a security policy, and does not declare workflow token permissions; these are meaningful transparency and maintenance concerns, though some omissions are reasonable for a minimal configuration package. Overall, it appears usable to depend on, with moderate abandonment and project-continuity risk rather than evidence that it is unfit.

Latest 2.2.1

Packagist

78%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Maintainers

Only one registry publishing account is listed, which limits visible publishing redundancy. However, the linked repository is organization-owned, making a short registry maintainer list less concerning for project backing.

Package scaffolding

A 2,720-character README explains installation, usage, and risky-rule behavior, which is useful for this configuration package. Tests and a changelog are absent in both the artifact and repository, creating a modest maturity gap.

Repo commit activity

The repository recorded 0 commits and 0 active maintainers in the last three months, which is a concrete sign of currently thin maintenance activity. The recent release and repository push provide some compensating evidence, but not enough to make this fully healthy.

Repo issue activity

There are no open issues or pull requests and no activity in the last month. This is not inherently negative for a small stable configuration, but it provides little evidence of an engaged maintenance community.

Repo popularity

The repository has only 1 star, 0 forks, and 1 watcher, so external adoption and community validation are minimal. Popularity is supporting evidence rather than decisive, but this increases continuity risk for a dependency.