liujinyong/ali-api

Release historycaution

Only three releases appeared, all within roughly five days, and none were published in the last two years. That short burst followed by a long release gap raises maintenance risk.

Repo commit activitycaution

The repository recorded no commits and no active maintainers in the last three months, consistent with the long release gap and suggesting the project is dormant.

Repo popularitycaution

The repository has zero stars and forks and only one watcher. Popularity is not required for a healthy package, but these figures provide little supporting evidence of community use or oversight.

Repo toolingcaution

Composer build tooling is present, but no security-scanning tools were detected. For a package handling cloud API integrations, that weakens automated maintenance hygiene.

Security policycaution

The repository has no security policy, leaving users without a documented vulnerability-reporting path. This is a transparency gap, though it is less serious than an archived or deprecated project.