ericjank/baidusdk

Release historydanger

The package has 7 releases, but its latest release was about 6 years and 8 months ago, with no releases in the last 12 months. This is strong evidence of abandonment for a dependency expected to receive maintenance.

Repo commit activitydanger

The repository recorded 0 commits and 0 active maintainers in the last 3 months, consistent with the long release gap and leaving no evidence of current maintenance capacity.

Package scaffoldingcaution

The artifact includes a README, but it is only 10 characters long and provides little consumer guidance. No tests or changelog are present; those omissions are normal for a published package, while the GitHub release confirms some release documentation practice.

Repository archivedcaution

The repository is not archived, which avoids the strongest explicit abandonment marker, but its last push was about 6 years and 9 months ago and does not compensate for the missing recent activity.

Security policycaution

The repository has no security policy, reducing transparency for reporting and handling vulnerabilities. This is a secondary hygiene gap beside the more substantial maintenance concern.