baimuze/think-baimuze-system

Release historydanger

The package has had no release in more than three years, with zero releases in the last 12 months; this is strong evidence of abandonment risk.

Repo commit activitydanger

There have been zero commits and zero active maintainers in the last three months, indicating that maintenance has stopped rather than merely slowed.

Repo package mentiondanger

The repository name does not match the package name and its README does not mention the package, creating uncertainty that the linked source is the package's actual project.

Project backingcaution

The repository is owned by an individual user rather than an organization, so there is no observed organizational backing to offset the single-maintainer and inactivity concerns.

Repo issue activitycaution

There are no open issues or pull requests and no activity in the last month; while quiet issue tracking is not inherently bad, it provides no evidence of active support.