jzh1/dingtalk

The MIT license, focused dependency set, README, repository tests, and release notes provide useful transparency. Long-term inactivity and the lack of security policy or scanning leave substantial abandonment and maintenance concerns.

Latest 1.1.2

Packagist

45%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

The package has made no releases in the last 12 months, and its latest release was about six years ago. Four releases in its first day show an initially brief burst rather than sustained maintenance.

Repo commit activity

The repository recorded zero commits and zero active maintainers in the last three months, consistent with the roughly six-year gap since its last push. No newer activity is provided to offset the abandonment concern.

Repo popularity

The repository has 0 stars, 0 forks, and 1 watcher, offering little supporting evidence of an active user or contributor community. Popularity is only supporting evidence, but it does not compensate for the inactivity.

Repo tooling

Composer build tooling is present, but no security scanning tools are reported. The missing scanning reduces maintenance assurance, especially alongside the lack of recent activity.

Security policy

The repository has no security policy, reducing transparency for reporting and handling vulnerabilities. This is a meaningful hygiene gap for a network-facing SDK, although it is not evidence of a security incident.