Package Health/helsingborg-stad/wp-page-for-posttype

helsingborg-stad/wp-page-for-posttype

This release appears suitable for dependency use: it has a long release history, seven releases in the last 12 months, a current stable version, an active non-archived repository, automated build and security tooling, tests in both the artifact and repository, and clear organizational backing. The main reservations are zero commits and active maintainers reported in the last three months, low repository popularity, no security policy, and incomplete top-level GitHub Actions permissions; these are meaningful hygiene and continuity concerns but are partly offset by the very recent release, a recently merged pull request, and the repository's established structure.

Latest 2.0.16

Packagist

82%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Repo commit activity

There were zero commits and zero active maintainers in the last three months, which is a caution for ongoing maintenance capacity. However, the latest release is very recent and the repository recorded a merged pull request during the last month, partly mitigating the concern.

Repo popularity

The repository has only 4 stars and 1 fork, indicating limited external adoption and review. Popularity is supporting evidence rather than a decisive health criterion, so this modestly lowers confidence in broad community validation.

Security policy

No security policy was found in the repository, leaving vulnerability-reporting expectations and response procedures undocumented.

Token permissions

The release workflow lacks top-level permissions and relies on job-level permissions, with no read-only workflow classification. This is a workflow-hardening gap, though no top-level write permissions were detected.