denis156/fcm-notification

Maintainerscaution

Only one registry publishing account is listed, and the repository is owned by that same individual. This is plausible for a small package but leaves little visible publishing redundancy.

Project backingcaution

The registry namespace and repository owner match, and the owner is an individual rather than an organization. The matching ownership supports provenance, while the individual backing limits visible organizational continuity.

Release historycaution

All three releases arrived within about two days, and no later release is shown during the package's roughly five-month history. This brief burst followed by a long quiet period raises maintenance uncertainty.

Repo toolingcaution

Composer is used as the build tool, but no security-scanning tool is detected. The missing scanner is a modest transparency and hygiene gap rather than evidence that the release is unsafe.

Security policycaution

The repository has no security policy. For a plugin handling notification credentials and native integration, this makes vulnerability reporting and response expectations less clear.