wpdesk/wp-mutex

This is a generally healthy, usable dependency with a long package history, a stable 2.0.0 release, an active non-archived organization-backed repository, clear licensing, minimal runtime dependencies, and strong source and artifact scaffolding. The repository contains unit and integration tests even though tests are not packaged, and its workflow uses read-only token permissions without the analyzed dangerous patterns. The main concerns are the small release history, no commits or active maintainers in the last 3 months despite a recent release, zero observed repository popularity, and the absence of a security policy or security-scanning tooling; these warrant monitoring but do not currently make the package unfit to adopt.

Latest 2.0.0

Packagist

78%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

The package has existed since October 2018 and has a release as recent as September 2026, but only four releases overall and one in the last 12 months indicate a relatively sparse release cadence.

Repo commit activity

No commits and no active maintainers were observed in the last 3 months, which is a maintenance concern; however, the repository was recently pushed and the registry shows a current release, partly compensating for the short-term commit gap.

Repo popularity

The repository has zero stars, forks, and watchers. Popularity is supporting evidence rather than a verdict, but the absence of any observed adoption signal modestly reduces confidence in long-term external validation.

Repo tooling

Composer build tooling is used, but no security-scanning tools were detected. The missing scanning is a hygiene gap, though it is not by itself evidence that the package is unsafe.

Security policy

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