Package Health/giofreitas/wordpress-composer-setup

giofreitas/wordpress-composer-setup

The package has a clear README, a declared MIT license, and a source repository that matches its name. Its small codebase lacks tests, security scanning, and a security policy, increasing maintenance uncertainty.

Latest 0.2

Packagist

43%

Total Score

Maintainer Stability

Maturity

Supply Chain

Health Score Breakdown

Release history

Only two releases were published, and none appeared in the last seven years; the latest release was published in May 2019. This is strong evidence of abandonment risk for a package that configures WordPress installations.

Repo commit activity

The repository recorded zero commits and zero active maintainers in the last three months, consistent with the long gap since the latest release. The repository is not archived, but there is no recent development activity to offset the concern.

Maintainers

One individual has registry publishing access. That is not inherently unhealthy, but it leaves little visible publishing capacity when combined with the absence of recent releases and commits.

Repo popularity

The repository has one star and no forks, providing little community evidence or outside maintenance support. Popularity is only supporting evidence, so this reinforces rather than determines the abandonment concern.

Repo tooling

Composer is used for the build, but no security-scanning tool is configured. This is a modest transparency and maintenance gap, not evidence that the package is unsafe by itself.