Package Health/pop-cms-schema/settings-wp

pop-cms-schema/settings-wp

This is a healthy, actively maintained release with a long history, frequent recent releases, stable versioning, explicit licensing, matching source repository, and recent commit activity. The repository is organization-owned and not archived, and the package has a small, understandable dependency profile with no install-time lifecycle scripts. The main concerns are that all recent commits come from one contributor, there is no repository security policy or security-scanning tooling, and the repository has minimal public popularity and issue activity; these reduce resilience and transparency but do not outweigh the strong release and maintenance evidence.

Latest 19.2.4

Packagist

82%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Maintainers

Only one registry account has publish access. This is a modest operational concentration, but it is less concerning because the source project is organization-owned and actual repository activity is available.

Repo bus factor

All 16 commits in the last 3 months were made by one contributor, creating a real continuity risk. Organization ownership provides some capacity for handoff, but no second active contributor is shown.

Repo popularity

The repository has 0 stars and 0 forks, with 1 watcher. This is weak supporting evidence, but popularity is not decisive and the package has strong release and commit activity.

Repo tooling

Composer is used as a build tool, but no security-scanning tools are detected. The absence of scanning lowers supply-chain hygiene, while the build tooling itself is appropriate for the package ecosystem.

Security policy

The repository has no SECURITY.md or other detected security policy, leaving vulnerability-reporting expectations less transparent.