surprise-tech/dingtalk_api

Release historydanger

The package has had 7 releases, but none in the last 12 months; its latest release was about 2 years and 5 months ago. This is meaningful abandonment risk despite the earlier rapid release cadence.

Maintainerscaution

Only one registry account has publish access, which is a limited publishing base. Because the repository is organization-owned, this is consistent with centralized publishing rather than strong evidence of abandonment.

Repo commit activitycaution

The repository recorded no commits and no active maintainers in the last 3 months, indicating that maintenance has currently stopped. The repository is not archived, but that does not offset the lack of recent work.

Repo toolingcaution

Composer build tooling is present, but no security scanning tools were detected. The build setup supports reproducibility, while the missing scanning reduces assurance around ongoing maintenance.

Security policycaution

The repository has no security policy, leaving vulnerability reporting and response expectations unclear. This is a transparency gap, though it does not by itself make the release unfit.