xyj2156/k3cloud-client

This release is usable and reasonably transparent, with an MIT license, a matching source repository, a complete-looking PHP package structure, repository tests, a changelog, no install-time scripts, no deprecation status, and no detected dangerous workflow patterns. However, it is extremely new with only two releases, has no demonstrated three-month commit activity or community activity, and lacks a security policy and explicit workflow token permissions; these gaps make maintenance and security-process maturity difficult to establish, so adoption should be accompanied by normal dependency monitoring and review.

Latest v1.0.1

Packagist

72%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Project backing

The repository is owned by an individual user rather than an organization, so there is no organizational backing signal to offset the very limited observed maintenance history.

Release history

The package is effectively 0 days old and has only two releases, so there is not yet enough release history to demonstrate sustained maintenance or compatibility practice.

Repo commit activity

There were zero commits and zero active maintainers in the measured three-month window, although the repository was pushed recently and the package is only 0 days old; this leaves sustained maintenance unproven rather than establishing abandonment.

Repo issue activity

There are no open issues or pull requests and no recent issue or PR activity. For a package this new, this is inconclusive, but it also means there is no demonstrated community support or maintenance responsiveness.

Repo popularity

The repository has zero stars, forks, and watchers. Because the package is newly published, this is weak evidence rather than a standalone abandonment verdict, but it provides no external adoption support.