Package Health/spryker/sales-payment-gui

spryker/sales-payment-gui

Healthy and suitable to use, backed by an active organization-owned repository and recent work from five contributors. The main caveats are a sparse release history, no tests, and limited repository security-policy and workflow-permission hygiene.

Latest 1.1.1

Packagist

82%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Package scaffolding

A README and changelog are present and the repository uses GitHub Releases, but neither the artifact nor repository contains tests. For a controller module, that is a genuine maintenance and regression-testing gap.

Release history

The package has existed for about 5 years but only has 3 releases, with a median interval of about 974 days and one release in the last 12 months. The recent release prevents this from indicating abandonment, but the cadence is sparse.

Repo issue activity

There were no new or closed issues or pull requests in the last month, and no pull requests were merged. This provides little evidence of active community maintenance, though issue counts are partly unknown.

Repo popularity

The repository has 0 stars and 0 forks, indicating limited public adoption. This is supporting evidence only and is outweighed by recent activity and organization backing.

Repo tooling

Composer build tooling is present, but no security-scanning tool was detected. The missing scanner is a transparency and defense-in-depth gap, not evidence that the package is unsafe.