mohamedsamy902/laravel-pulse-alert

Repo commit activitydanger

The repository recorded zero commits and zero active maintainers in the last three months. With only a short release history, this is meaningful evidence of weak current maintenance.

Maintainerscaution

Only one registry account has publish access. That is a narrow publishing base; the repository is also owned by an individual rather than an organization, so there is no provided backing signal to offset the concentration.

Project backingcaution

The linked repository is owned by a user account, not an organization. This does not imply abandonment, but it provides less visible continuity than organizational backing when recent activity is absent.

Release historycaution

All four releases arrived within about one day, and there has been no later release during the package's roughly six-month lifetime. This is a limited maintenance track record rather than evidence of established stability.

Repo toolingcaution

Composer build tooling is present, but no security scanning tools were detected. The missing scanner is a modest transparency and assurance gap for a package handling alerts and application data.