roiwk/umeng-open-api

Release historydanger

There has been only one release, published about 5 years and 9 months ago, with no releases in the last 12 months. This is strong evidence of abandonment risk for a library dependency.

Repo commit activitydanger

There were zero commits and zero active maintainers in the last 3 months, consistent with the long release gap and indicating no observed ongoing maintenance.

Maintainerscaution

Only one registry account has publishing access. That is a thin publishing base and increases continuity risk when repository activity is already inactive.

Repo popularitycaution

The repository has 2 stars and 1 fork, providing little external evidence of adoption or review. Popularity is supporting evidence only, so this modestly reinforces—but does not determine—the maintenance concern.

Repo toolingcaution

Composer build tooling is present, but no security scanning tools were detected. This is a modest transparency and maintenance weakness rather than a standalone severe risk.