private

Release historydanger

The latest registry release was in October 2017, with no releases in the last 12 months. That long publishing gap materially raises abandonment and compatibility risk.

Repo commit activitydanger

The repository recorded zero commits and zero active maintainers in the last three months, reinforcing the risk suggested by the old registry release history.

Maintainerscaution

One registry maintainer is consistent with a small project, but it leaves little visible publishing redundancy if that maintainer becomes unavailable.

Project backingcaution

The repository is owned by an individual rather than an organization, so there is no organizational backing signal to offset the thin maintainer base.

Repo issue activitycaution

There are three open issues and one open pull request, with no issues or pull requests merged in the last month. This suggests limited current responsiveness.