gitlexin/jpush-api-php-client

Release historydanger

The latest release was published in March 2020, with no releases in the last 12 months despite the package being over six years old. This is strong evidence of abandonment risk.

Repo commit activitydanger

The repository recorded zero commits and zero active maintainers in the last three months, consistent with the release history showing no activity since March 2020.

Project backingcaution

The registry namespace and repository owner match, but the owner is an individual account rather than an organization, providing limited evidence of ongoing project backing.

Repo toolingcaution

Composer is used for builds, but no security scanning tool is present. This is a modest transparency and maintenance gap, not a severe risk by itself.

Security policycaution

The repository has no security policy, leaving vulnerability-reporting expectations unclear. This matters for a network-facing API client, although it does not prove the code is unsafe.