Package Health/conductor/wordpress-platform-support

conductor/wordpress-platform-support

This is a generally healthy, actively maintained release: it has a long history since 2018, four releases in the last 12 months, a stable non-prerelease version, recent repository activity, an organization-owned source repository, clear licensing, tests, changelog, and no install-time lifecycle scripts or registry deprecation. The main concerns are that all recent commits come from one contributor, the repository has no security scanning or security policy, and the linked repository neither matches the package name exactly nor mentions the package in its README, which weakens transparency. These issues warrant caution but are partly offset by the organization's project backing and the package's otherwise complete artifact and repository structure.

Latest 5.0.0

Packagist

78%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Repo bus factor

All 3 recent commits came from one contributor, creating concentration risk; the organization-owned repository provides some ability to hand maintenance off, so this is caution rather than danger.

Repo issue activity

There are no open issues and one open pull request, but no issues or pull requests were closed or merged in the last month; this gives only limited evidence of community responsiveness.

Repo package mention

The repository name does not match the package name and its README does not mention the package, creating a concrete transparency concern about whether the repository directly represents this package. The mismatch is not conclusive by itself, but the lack of a README mention makes caution appropriate.

Repo popularity

The repository has no stars or forks and only 7 watchers, indicating limited external adoption evidence; popularity is supporting evidence, so this is a minor concern rather than a health verdict.

Repo tooling

Composer is used as a build tool, but no security-scanning tools are detected. The build setup is appropriate, while the missing scanning coverage is a transparency and security-hygiene gap.