tiger/cmq

Release historydanger

There has been only one release, published about 9 years ago, with no releases in the last 12 months. This is strong evidence of abandonment or unmaintained compatibility.

Repo commit activitydanger

There were zero commits and zero active maintainers in the last 3 months, consistent with the repository's last push about 9 years ago and indicating severe maintenance inactivity.

Maintainerscaution

One registry maintainer provides a thin publishing base, and the project is user-backed rather than organization-backed, so there is little visible redundancy if that maintainer stops maintaining it.

Package scaffoldingcaution

A consumer-facing README is present, but the package and repository have no tests or changelog; the missing tests are a meaningful maintenance gap for an integration library.

Project backingcaution

The repository is owned by an individual user rather than an organization, so there is no organizational backing shown to compensate for the single maintainer and absent activity.