php-cuong/magento2-faqs-extensions

Release historydanger

The package has had no releases in the last 12 months, and its latest release was in 2017 despite being about nine years old. This is strong evidence of abandonment risk.

Repo commit activitydanger

The repository had zero commits and zero active maintainers in the last three months. Combined with the old last push, this materially increases abandonment risk.

Maintainerscaution

Only one registry account has publishing access. Because the repository is user-owned rather than organization-backed, this represents a thin publishing and continuity base.

Project backingcaution

The registry namespace and repository owner both identify the same individual account. That supports ownership consistency, but provides no organizational backing to compensate for the single-maintainer base.

Repo toolingcaution

Composer is used as a build tool, but no security scanning tools were detected. This is a modest transparency and maintenance-hygiene gap, not evidence of unsafe code by itself.