gopay-libs/gopay-ui

This is a usable and reasonably transparent young package, but not yet a mature dependency. The release is stable and recently published, the repository is active, unarchived, clearly matches the package, and the artifact includes documentation, tests, a changelog, licensing, and no install-time lifecycle scripts. However, the project is only 81 days old with three releases, has no observable community activity or popularity, relies on a single registry maintainer, and lacks repository security scanning and a security policy. These gaps warrant caution for a payment-related Laravel dependency, although the available evidence does not indicate abandonment or registry deprecation.

Latest v1.0.2

Packagist

72%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Maintainers

Only one registry account, GoPay, has publish access. This is a thin publishing base, although the organization-backed repository provides some compensating project ownership context.

Release history

The package is young at 81 days and has only three releases, with a median interval of about 41 days; this limits maturity evidence, though the latest release was published recently and releases are ongoing.

Repo issue activity

There are no open issues or pull requests and no issue or pull-request activity in the last month. This is not evidence of abandonment by itself, but it also provides no demonstrated community support.

Repo popularity

The repository has zero stars, forks, and watchers. Popularity is supporting evidence rather than a verdict, but these values provide no external adoption or durability evidence for this young package.

Repo tooling

Composer is used as the build tool, which fits the PHP package, but no security scanning tools are configured. The missing scanning reduces supply-chain transparency for a payment-related package.