maxlord/yii2-jsviews

Release historydanger

The package is over 11 years old but has only three releases, all clustered on its first release day, with no releases in the last 12 months. This is strong evidence of abandonment risk, although the package is not marked deprecated.

Repo commit activitydanger

There were zero commits and zero active maintainers in the last three months, against a last push in September 2015. This indicates prolonged inactivity and materially raises abandonment risk.

Project backingcaution

The package and repository are owned by the same individual account, with no organization backing shown. This is not inherently unhealthy, but it offers limited visible maintenance capacity for a package already showing prolonged inactivity.

Repo popularitycaution

The repository has zero stars and forks and only one watcher. Popularity is supporting evidence rather than a verdict, but these counters provide no meaningful community-maintenance signal.

Repo toolingcaution

Composer build tooling is present, but no security scanning tools are configured. For an old package with no recent activity, that absence weakens ongoing transparency and maintenance hygiene.