Package Health/stackout/kubernetes-client

stackout/kubernetes-client

Risky to adopt: the package has had no release or repository activity for nearly seven years and remains a prerelease. It has useful documentation, tests, an MIT declaration, and no install-time scripts, but those positives do not offset the lack of ongoing maintenance.

Latest 0.16

Packagist

38%

Total Score

Maintainer Stability

Maturity

Supply Chain

Health checks

Release history

The package has 55 releases, but none in the last 12 months; its latest release was in November 2019, nearly seven years before collection. This is strong evidence of abandonment for a Kubernetes client that must track a changing platform.

Repo commit activity

The repository recorded zero commits and zero active maintainers during the last three months. Combined with the old last push and release history, this indicates no current maintenance capacity.

Repository archived

The repository is not marked archived, but its last push was in November 2019. The non-archived status does not compensate for the absence of recent development.

Repo issue activity

There were no new issues, pull requests, or merged pull requests in the last month, and no pull requests were open. This is consistent with an inactive project, although the missing open-issue count limits visibility.

Repo tooling

Composer and Phing build tooling are present, but no security-scanning tools are configured. The build tooling is a positive maturity signal; the absent scanning is a minor transparency gap rather than a standalone severe risk.