brorand

Release historydanger

The package has had no release in over 9 years, with the latest release in February 2017; this is the clearest abandonment concern.

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 current maintenance capacity.

Maintainerscaution

Only one registry account has publish access. That is a thin operational base and increases continuity risk when combined with the absence of recent activity.

Project backingcaution

The repository is owned by an individual rather than an organization, so the single-maintainer structure represents a real continuity limitation rather than normal organizational publishing hygiene.

Repo issue activitycaution

There was no issue or pull-request activity in the last month, while two issues and two pull requests remain open; this suggests limited ongoing support.