tanujdave/notify

Release historydanger

The package has only 3 releases, all concentrated in March 2018, with no releases in the last 12 months and a median interval of about 33 minutes. This strongly indicates abandonment risk.

Repo commit activitydanger

The repository recorded zero commits and zero active maintainers during the last 3 months, consistent with the last push occurring in March 2018. This is a substantial ongoing-maintenance concern.

Dependency profilecaution

The package declares four runtime dependencies and no development dependencies. This is a modest dependency surface, though the absence of development dependencies provides little evidence of a maintained test or validation setup.

Maintainerscaution

One registry account has publish access. This is a limited publishing base, but the signal describes access rather than actual maintenance activity and is outweighed by the repository activity evidence.

Project backingcaution

The repository is owned by an individual account rather than an organization. That does not establish poor health by itself, but it provides no organizational backing to offset the lack of recent activity.