bgkavinga/magento2-patches

Release historydanger

The latest release was published over 9 years ago, with no releases in the last 12 months; this is strong evidence of abandonment risk for a patch package.

Repo commit activitydanger

There were no commits and no active maintainers in the last 3 months, corroborating the long release gap and materially increasing abandonment risk.

Repo issue activitycaution

There were no new issues or pull requests in the last month. With no recent commits or releases, this suggests the project is inactive rather than simply quiet in issue tracking.

Repo popularitycaution

The repository has only 1 star and 1 fork, offering little evidence of broad community review or ongoing support.

Repo toolingcaution

Composer is used for builds, but no security scanning tools are present. This is a hygiene gap that matters more for a package distributing executable patching code.