fivesqrd/mutex

This is a generally usable and transparently packaged release: it has a stable version, a linked non-archived repository owned by an organization, a license file, tests in both the artifact and repository, a lean runtime dependency profile, and no install-time scripts or dangerous workflows. The main concerns are limited recent development activity, very low repository adoption, the absence of a security policy, and no changelog; these reduce confidence in ongoing maintenance and security-response capacity, although the release and repository were updated recently and the package is not deprecated.

Latest v1.0.14

Packagist

74%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

The package has existed for about 9 years with 19 releases, and one release occurred in the last 12 months, including the assessed release. The relatively sparse long-term release cadence warrants some caution about maintenance velocity, despite the recent publication.

Repo commit activity

There were zero commits and zero active maintainers in the last 3 months. Although the repository was pushed recently and a new release was published, the measured development inactivity raises a meaningful maintenance and abandonment concern.

Repo issue activity

There are no open issues or pull requests and no activity in the last month. This is not inherently unhealthy for a small stable library, but it also does not demonstrate an active user or maintainer feedback loop.

Repo popularity

The repository has zero stars and forks and only one watcher. Popularity is not decisive, but these figures provide little supporting evidence of broad adoption or community depth.

Repo tooling

Composer is used as a build tool, but no security scanning tool is detected. The missing scanning automation is a security-hygiene gap, though it is not evidence of maliciousness or an immediate dependency-health failure.