lukasz/gus

Release historydanger

The package has had four releases, all concentrated on 27 November 2019, with no releases in nearly seven years. This strongly indicates abandonment risk despite the stable 1.7 version.

Repo commit activitydanger

There were zero commits and zero active maintainers in the last three months, consistent with the nearly seven-year release gap. This is a substantial maintenance and abandonment concern.

Project backingcaution

The repository is owned by an individual user rather than an organization. That is not inherently unhealthy, but it provides less visible institutional backing 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 decisive, but these counters provide no community-maintenance signal to compensate for the inactivity.

Repo toolingcaution

Composer build tooling is present, but no security-scanning tooling was detected. The missing scanner is a modest transparency and hygiene gap, not evidence that the package is unsafe.