muneebkh2/laravel-fcm-notifications

Release historycaution

The package has six releases since October 2024, but none in the last 12 months; the latest release was about 19 months ago. This supports an established release history but raises a current-maintenance concern.

Repo commit activitycaution

The repository recorded zero commits and zero active maintainers in the last three months, consistent with a project whose activity has stopped. This is the main abandonment concern.

Repo toolingcaution

Composer is used for builds, but no security scanning tools are configured. The missing scanning is a modest transparency and hygiene gap, not evidence of unsafe behavior by itself.

Security policycaution

The repository has no security policy, leaving no documented process for reporting or handling vulnerabilities. For a package that handles Firebase credentials, this is a meaningful transparency gap.

Workflow auditcaution

No GitHub Actions workflows were present, so there were no workflow risks to flag; this also means there is no automated workflow evidence supporting ongoing maintenance.