Package Health/spryker/product-extension

spryker/product-extension

This is a healthy, actively backed package release with a stable version, current publication, a non-archived organization-owned repository, recent activity from five contributors, and low contributor concentration. The package has coherent source and artifact structure, a license file, no install-time lifecycle scripts, a minimal dependency profile, and no detected dangerous workflow patterns. The main reservations are sparse release cadence, no tests in either the artifact or repository, absent security scanning and security policy, and undeclared top-level GitHub Actions permissions; these are meaningful hygiene gaps but do not outweigh the strong maintenance and project-backing evidence.

Latest 1.6.0

Packagist

84%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Package scaffolding

The package includes a README and changelog, and the repository also has a changelog and uses GitHub Releases. Tests are absent in both places, which is a modest quality concern for a package providing extension interfaces.

Release history

The package has existed for about 5 years and its latest release was published today, but only one release occurred in the last 12 months and there are seven releases overall, indicating a relatively sparse cadence.

Repo issue activity

There are no new or closed issues or pull requests in the last month and no open pull requests. This gives little evidence of community interaction, though it does not establish abandonment because recent commits are present.

Repo popularity

The repository has zero stars and forks and four watchers. This is weak supporting popularity evidence, but popularity is not decisive and the package has stronger maintenance and organization-backing signals.

Repo tooling

Composer build tooling is present, but no security-scanning tools were detected. The build setup is established while security automation remains a hygiene gap.