youngyezi/mutex

Its MIT license, minimal dependency surface, and matching repository make the contents easy to inspect. The lack of security policy and project activity leaves maintenance responsibility with a single apparent publisher.

Latest v1.0.0

Packagist

39%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

This package has had one release, published over seven years ago, with no releases in the last 12 months. That is strong evidence of abandonment risk for a dependency.

Repo commit activity

There were no commits and no active maintainers in the last three months, consistent with a project that has been inactive for years. This materially increases the risk that defects will remain unaddressed.

Project backing

The repository is owned by a user account rather than an organization, so there is no provided evidence of broader project backing to compensate for the single-publisher context.

Repo popularity

The repository has zero stars and forks and only one watcher. Popularity is supporting evidence rather than a verdict, but these counters provide little evidence of external review or adoption.

Repo tooling

Composer is used for the build, but no security scanning tools are configured. The missing scanning is a modest transparency and maintenance gap rather than proof of unsafe code.