Package Health/ricardomartins/pagbank-woocommerce

ricardomartins/pagbank-woocommerce

This is a healthy, actively maintained release with strong release cadence, a stable version, a non-archived linked repository, clear licensing, substantial package scaffolding, and explicit security-policy documentation. The main dependency risk is concentration: all 13 recent commits came from one contributor, and the repository's workflow lacks top-level token permissions and security-scanning tooling. Those concerns warrant operational diligence but are outweighed by frequent recent releases, current repository activity, tests, changelog and README coverage, and the absence of registry deprecation or dangerous workflow patterns.

Latest 4.57.4

Packagist

84%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Project backing

The repository is owned by a user rather than an organization, so there is no organizational handoff capacity to offset the concentrated maintainer base.

Repo bus factor

One contributor owns 100% of the 13 commits in the last 3 months, creating a meaningful single-maintainer continuity risk for a user-owned project.

Repo issue activity

There are no open issues or pull requests, but there was also no issue or pull-request activity in the last month; this is neutral-to-slightly limited evidence rather than a demonstrated maintenance failure.

Repo popularity

The repository has 4 stars, 4 forks, and 3 watchers. This is limited supporting popularity evidence, but popularity is not required for a small package and does not outweigh its strong release activity.

Repo tooling

Composer is used as a build tool, but no security-scanning tools were detected. The missing scanning coverage is a hygiene gap, though it is not by itself evidence of unsafe code.