peec/aws-laravel-notification

Release historydanger

The package has four releases, all concentrated on December 26, 2016, and none in the last 12 months. A release gap of more than 9 years is strong evidence of abandonment risk.

Repo commit activitydanger

The repository recorded zero commits and zero active maintainers in the last 3 months, consistent with the release history and indicating no observed ongoing maintenance.

Repo issue activitycaution

There were no new or closed issues or pull requests in the last month, while two issues remain open. This provides no evidence of active support.

Repo toolingcaution

Composer build tooling is present, but no security-scanning tools are configured. That weakens maintenance transparency, although it is not by itself evidence that the package is unsafe.

Security policycaution

The linked repository has no security policy. This is a transparency and vulnerability-reporting gap, especially for a package handling cloud-service credentials.