Package Health/alibabacloud/dianjin-20240628

alibabacloud/dianjin-20240628

This release appears suitable to depend on: it is actively released, stable, not deprecated, licensed under Apache-2.0, and backed by a matching organization-owned repository that was pushed very recently. The main concerns are the very small recent commit/contributor base, absence of repository security scanning and a security policy, lack of tests, and minimal repository popularity; these are meaningful transparency and resilience gaps, but they are partly offset by the package's strong release cadence, coherent generated-SDK structure, organization backing, and absence of risky lifecycle scripts or workflows.

Latest 1.22.0

Packagist

78%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Package scaffolding

README and changelog documentation are present and the repository uses GitHub Releases, although neither the artifact nor repository contains tests. For an SDK this is a modest maintainability gap rather than a severe release risk.

Repo bus factor

All two recent commits came from one contributor, creating a concentrated operational dependency. Organization ownership partially compensates because maintenance can be handed off internally, but the observed recent base remains thin.

Repo commit activity

Only two commits occurred in the last three months, showing low recent repository activity, although the repository was pushed recently and the release history shows frequent package releases.

Repo issue activity

There were no new or closed issues or pull requests in the last month and no merged pull requests; this indicates limited community interaction, although the open-issue count is unknown and the package is maintained through direct releases.

Repo popularity

The repository has zero stars and forks and only three watchers, which provides little external adoption evidence. Popularity is supporting evidence, so this is a caution rather than a standalone health failure.