mayoz/laravel-omnipay

Release historydanger

Only two releases were published, with the latest in January 2016 and none in the last 12 months. This is strong evidence of abandonment for a framework integration that may need to track its ecosystem.

Repo commit activitydanger

The repository recorded zero commits and zero active maintainers in the last three months, consistent with the long release gap and indicating no current maintenance capacity.

Repo toolingcaution

The repository uses Composer, but no security scanning tooling is present. This is a minor transparency and maintenance gap rather than a severe risk for this small package.

Security policycaution

No security policy is present in the repository. That limits the documented process for reporting vulnerabilities, although it does not by itself show that the package is unsafe.