openiap/client

The linked repository has no security policy or scanning, and its name does not match the package or clearly mention it. The native-library layout makes missing tests and changelog understandable, but consumer documentation remains thin.

Latest 0.0.38

Packagist

40%

Total Score

Maintainer Stability

Maturity

Supply Chain

Health Score Breakdown

Release history

The latest release was about 16 months ago, with no releases in the last 12 months, despite 11 releases in the package's earlier history. That sharp halt materially raises abandonment risk.

Repo commit activity

The repository recorded zero commits and zero active maintainers in the last three months. Combined with the absence of releases for about 16 months, this is strong evidence that maintenance has stopped.

Repo package mention

The repository name does not match the package name, and no README package mention was available. A monorepo or subpackage could explain the mismatch, but the package-to-source relationship is not clearly established.

Repo popularity

The repository has zero stars and forks and one watcher. Popularity is only supporting evidence, but these counts provide little external evidence of maturity or community support.

Repo tooling

Composer is used as the build tool, which fits the package, but no security scanning tools were detected. That is a transparency and maintenance-hygiene gap, though not evidence of compromise by itself.