crodas/dispatcher

Release historydanger

The latest release was in April 2016, with no releases in the last 12 months. This long release gap is strong evidence of abandonment risk despite the package having 31 historical releases.

Repo commit activitydanger

There were zero commits and zero active maintainers in the last three months, consistent with the repository having stopped receiving changes years ago.

Dependency profilecaution

Six runtime dependencies create a meaningful upkeep and compatibility burden for an old package, especially when its own maintenance has stopped.

Maintainerscaution

Only one registry account has publish access. That is a narrow publishing base, although the linked repository is also owned by the same individual, so it is consistent rather than contradictory.

Project backingcaution

The registry namespace and repository are both owned by the same individual, providing consistent ownership context. Individual ownership does not provide the resilience of organizational backing.