Package Health/bitmicrosys/sharpsports-php

bitmicrosys/sharpsports-php

Clear documentation, tests, and licensing make integration easier. The project has had no release in 406 days after only two releases, with no recent issue or pull-request activity; its security practices are also undocumented.

Latest 1.0.1

Packagist

45%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

The package is 406 days old but has only two releases, both concentrated on its first day, and none in the last 12 months. This is strong evidence of limited ongoing maintenance for an SDK.

Project backing

The repository is owned by an individual account rather than an organization. This is not inherently unhealthy, but it means there is no provided organizational backing to compensate for the thin maintenance record.

Repo issue activity

There are no open issues or pull requests and no issue or pull-request activity in the last month. Combined with the stalled release history, this supports an abandonment concern.

Repo popularity

The repository has zero stars, forks, and watchers. This is only supporting evidence rather than a verdict, but it provides no external adoption signal to offset the maintenance gap.

Repo tooling

Composer is used as the build tool, but no security scanning tools are present. For a small package this is a hygiene gap, though it is less significant than the inactive release history.