chrys/notification

Release historydanger

Only two releases were published, both in October 2018, with no releases in roughly seven years. That is strong evidence of abandonment for a library dependency.

Repo commit activitydanger

The repository recorded zero commits and zero active maintainers in the last three months, consistent with the long release gap and limited maintenance capacity.

Repo popularitycaution

The repository has zero stars and forks and only one watcher. Popularity is not decisive, but this provides no supporting evidence of active community use.

Repo toolingcaution

Composer build tooling is present, but no security scanning tools were detected. This is a modest transparency and maintenance gap rather than a standalone adoption blocker.

Security policycaution

The repository has no security policy, leaving vulnerability reporting and response expectations undocumented. This adds a transparency gap for a package that sends email.