subretion/omnipay-bepaid

Maintainerscaution

Only one account has registry publish access, which is a narrow publishing base. The organization-owned repository provides some backing, so this is a modest resilience concern rather than a standalone abandonment signal.

Package scaffoldingcaution

The artifact has no README, tests, or changelog, and the repository reports none of these either. Missing tests and changelog are normal packaging practice, but the absent README is a real usability and transparency gap for a library consumers must integrate.

Repo commit activitycaution

There were no commits and no active maintainers in the last 3 months. The recent release push and release history partly compensate, but the lack of ongoing source activity lowers confidence in maintenance continuity.

Repo toolingcaution

The repository uses Composer for its build tooling, but no security scanning tools were detected. The missing scanning is a hygiene gap, not evidence that the release is unsafe.

Security policycaution

The repository has no security policy. For a payment-processing integration, this reduces transparency around vulnerability reporting and response.