yami/sheet-fight

Its MIT license, matching repository, and zero runtime dependencies reduce adoption friction. The small project has no security policy, so future fixes and oversight are limited.

Latest 1.2.0

Packagist

40%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

The latest release was in September 2015, about 11 years ago, with no releases in the last 12 months. That strongly raises abandonment risk despite five historical releases.

Repo commit activity

There were zero commits and zero active maintainers in the last three months, consistent with an effectively dormant project and a high risk of unfixed problems.

Project backing

The repository is owned by an individual account rather than an organization, so there is no provided evidence of broader project backing to compensate for the inactive maintainer base.

Repo issue activity

There has been no new or closed issue activity in the last month and one issue remains open, providing little evidence of current project support.

Repo tooling

Composer is used for the build, but no security scanning tools are present. This is a modest transparency and oversight gap for a package with no recent maintenance.