nlybe/river_grouping

Release historydanger

The package is about 9 years old, has only 2 releases, and has had no release in the last 12 months. This is strong evidence of abandonment risk for a dependency.

Repo commit activitydanger

The repository recorded 0 commits and 0 active maintainers in the last 3 months, consistent with the long release gap and providing no evidence of current maintenance.

Repo package mentioncaution

The repository name does not match the package name and its README does not mention the package, so the link between the registry package and source repository is less transparent.

Repo popularitycaution

The repository has 0 stars, 0 forks, and 1 watcher. Popularity is only supporting evidence, but these figures provide no meaningful community signal to offset the inactivity.

Repo toolingcaution

The repository uses Composer for builds, but has no security scanning tools. The build tooling is appropriate; the missing scanning is a minor hygiene gap rather than a primary health issue.