g3n1us/laravel-react-sync

Release historydanger

The latest release was published nearly seven years ago, with no releases in the last 12 months. This is strong evidence of abandonment risk despite four historical releases.

Repo commit activitydanger

There were no commits and no active maintainers in the last three months, with the repository last pushed nearly six years ago. This substantially limits confidence that defects or compatibility issues will be addressed.

Lifecycle scriptscaution

A post-autoload-dump lifecycle script runs during Composer installation. The signal does not show that it is unsafe, but install-time execution adds a small transparency and review concern.

Repo toolingcaution

The repository uses Composer for builds, but no security-scanning tools were detected. The missing scanning is a modest process gap, not evidence that the package is unsafe.

Security policycaution

The repository has no security policy. That weakens the documented process for reporting and handling vulnerabilities, though it is less severe than evidence of abandoned releases or commits.