Package Health/joshdifabio/magento1-composer-bridge

joshdifabio/magento1-composer-bridge

A one-person project has only a six-file package, a 28-character README, and no tests or security policy. The stable major version, single runtime dependency, and lack of install scripts reduce adoption friction but do not offset the maintenance concern.

Latest v1.2.0

Packagist

38%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

The package has made four releases since July 2015, but its latest release was in October 2016 and there were no releases in the last 12 months. This is strong evidence of prolonged inactivity.

Repo commit activity

There were zero commits and zero active maintainers in the last three months. Combined with the old latest release, this indicates that maintenance capacity is currently absent.

Maintainers

Only one registry maintainer is listed, and the project is user-owned rather than organization-backed. That leaves limited visible publishing and maintenance redundancy.

Package file tree

The package and repository each contain only six files, including the core PHP files and Composer metadata. This is consistent with a small bridge package, but provides little visible project depth.

Project backing

The registry namespace and repository owner match a single user account, with no organization backing shown. This provides direct ownership but limited evidence of institutional continuity.