bariew/yii2-i18n-cms-module

Release historydanger

Only two releases exist, with none in the last 12 months; the latest was published in June 2016. This is strong evidence of abandonment risk, although the repository is not archived.

Repo commit activitydanger

There were no commits and no active maintainers in the last three months, consistent with a project whose last known repository push was in 2019. This materially raises abandonment risk.

Maintainerscaution

One registry account publishes the package. That is not itself a defect, but it provides little visible redundancy for a project without recent activity.

Repo package mentioncaution

The repository name matches the package, but its README does not mention the package name. That weakens package-to-repository transparency, though the matching repository name is compensating evidence.

Repo toolingcaution

Composer build tooling is present, but no security scanning tooling was detected. This is a modest transparency and maintenance gap rather than evidence that the package is unsafe.