tencentcloud/yinsuda

Healthy and suitable to depend on, with strong release activity, clear licensing, and organizational backing. The main concerns are that one contributor made all recent commits and the repository has no tests or security policy.

Latest 3.0.1669

Packagist

78%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health checks

Package scaffolding

A README is present, but neither the package nor repository includes tests or a changelog. For an SDK this is a real maintenance and transparency gap, although the substantial generated source tree and frequent releases provide some context.

Repo bus factor

All 32 recent commits came from one contributor, so maintenance is concentrated. Organizational backing helps provide continuity, but no second active contributor is shown to reduce the handoff risk.

Repo issue activity

There are no open issues or pull requests and no recent issue or pull-request activity. This is not inherently negative for a generated SDK, but it provides little evidence of community review or support.

Repo popularity

The repository has zero stars, forks, and watchers, so there is little visible community adoption or support. Popularity is supporting evidence only, and the active release history partly offsets this weakness.

Repo tooling

Composer is used for the build, but no security scanning tools are present. The build tooling supports reproducibility, while the absent scanning is a modest transparency gap.