timkippdev/slack-notifier

Release historydanger

Only two releases were published, both in July 2019, and there have been no releases in more than seven years. That sharply increases abandonment and compatibility risk.

Repo commit activitydanger

There were zero commits and zero active maintainers in the last three months, consistent with no meaningful repository activity since July 2019.

Maintainerscaution

One registry maintainer is consistent with a small user-owned project, but it provides little redundancy if that maintainer stops supporting the package.

Project backingcaution

The package and repository are owned by the same individual account rather than an organization, so there is no visible organizational backing to offset the single-maintainer risk.

Repo issue activitycaution

There are no open issues or pull requests, and no recent activity. This may reflect a quiet stable project, but alongside the stale release and commit history it supports an abandonment concern.