Package Health/fballiano/magento2-category-sort-direction

fballiano/magento2-category-sort-direction

The repository remains identifiable, licensed, and documented, with no install-time scripts or deprecation. Maintenance evidence is thin: it has one release, no recent commits, and one registry maintainer; it also lacks security scanning and a security policy.

Latest 0.1.0

Packagist

62%

Total Score

Maintainer Stability

Maturity

Supply Chain

Health Score Breakdown

Maintainers

One registry maintainer is consistent with a small, user-owned project, but it provides limited redundancy if that maintainer becomes unavailable.

Project backing

The registry namespace and repository are owned by the same individual account, providing clear ownership but no organizational backing or maintainer redundancy.

Release history

The package has only one release, published about 4 years ago, with no releases in the last 12 months. This limits evidence of ongoing maintenance and compatibility work.

Repo commit activity

There were no commits and no active maintainers in the last 3 months. Combined with the single historical release, this indicates weak recent maintenance evidence.

Repo tooling

Composer is used as the build tool, which fits the package ecosystem, but no security scanning tools were detected. The missing scanning is a modest transparency and hygiene gap.