canerdogan/laravel-notification-channel-fcm

Release historydanger

The latest release was published about 6 years 10 months ago, with no releases in the last 12 months. Ten total releases show some history, but the long publication gap materially raises abandonment risk.

Repo commit activitydanger

The repository recorded zero commits and zero active maintainers in the last 3 months, consistent with the package's long release gap. This indicates inactive maintenance rather than a temporary slowdown.

Repo toolingcaution

The project uses Composer, which is appropriate for this package, but no security scanning tools were detected. The missing scanning is a hygiene weakness rather than evidence that the release is unsafe by itself.

Security policycaution

The repository has no security policy. This is a transparency and vulnerability-reporting gap, particularly for a notification integration, though it is secondary to the much stronger inactivity concern.