Package Health/koongo-com/magento2-data-feed-manager

koongo-com/magento2-data-feed-manager

This release is usable but warrants caution. The package has a substantial 1,503-day history, 27 releases, six releases in the last 12 months, stable versioning, an active non-archived organization-owned repository, and a recent release/push, which support ongoing maintenance. However, repository commit activity shows zero commits and zero active maintainers in the last three months, while the artifact and repository have no tests or changelog, no security policy, and no security scanning; these reduce transparency and make regression and abandonment risk harder to evaluate. The modest runtime dependency set, absence of install lifecycle scripts, clear licensing, and two recently merged pull requests are compensating evidence, so this is a viable dependency with operational review recommended rather than an outright liability.

Latest 2.4.9.11

Packagist

68%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Package scaffolding

A 3,818-character README and GitHub Releases provide useful usage and release context, but both the artifact and repository lack tests and a changelog. The missing tests and changelog are meaningful transparency gaps for a sizable Magento extension.

Repo commit activity

The repository records zero commits and zero active maintainers in the last three months, a significant concern because it conflicts with the recent release and push and may indicate a collapsed or inactive development workflow.

Repo popularity

The repository has 9 stars and 4 forks, indicating limited community adoption. Popularity is only supporting evidence, so this lowers confidence in external validation more than it determines health.

Repo tooling

Composer is used as a build tool, but no security scanning tools are configured. Build tooling is appropriate, while the missing security automation is a hygiene gap for a package handling store and catalog integrations.

Security policy

The repository has no SECURITY.md or equivalent security policy, leaving vulnerability-reporting and response expectations undocumented.