vrpayment/magento-2

This is a generally usable and actively maintained Magento payment extension, with 23 releases over about 671 days, 15 releases in the last 12 months, a current stable release, an unarchived repository, explicit Apache-2.0 licensing, and clear organization backing from VR Payment GmbH. The main concerns are that all five commits in the last three months came from one contributor, the repository has no tests, changelog, security policy, or security scanning, and repository popularity is very low. These gaps increase maintenance and transparency risk, but the recent release cadence, current repository activity, matching repository, and organization ownership provide meaningful compensation.

Latest 3.5.0

Packagist

72%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Package scaffolding

A substantial README and GitHub Releases are present, but neither the artifact nor repository contains tests or a changelog. For a payment integration, the absence of repository tests is a meaningful maintenance and verification gap; the release history provides only partial compensation.

Repo bus factor

One contributor made all 5 commits in the last three months, creating a clear short-term concentration risk. Organization ownership provides some potential handoff capacity, but no second active contributor is shown.

Repo issue activity

There were no new or closed issues and no pull requests in the last month; this is ambiguous because open issue count is unavailable, so it is a limited activity signal rather than strong evidence of neglect.

Repo popularity

The repository has only 1 star, 0 forks, and 3 watchers. Popularity is supporting evidence rather than a verdict, but these very low figures provide little external adoption signal.

Repo tooling

Composer is used as a build tool, but no security scanning tools are detected. Build tooling is appropriate, while the missing security scanning is a hygiene gap for payment-related software.