runn/fs

Release historydanger

The latest release was published about six years ago, with no releases in the last 12 months. This is strong evidence of abandonment risk for a library dependency.

Repo commit activitydanger

There were no commits and no active maintainers in the last three months, consistent with the release history and indicating a severe maintenance gap.

Repo issue activitycaution

There were no new or closed issues in the last month and one open pull request, providing no evidence of active issue maintenance.

Repo popularitycaution

The repository has only 5 stars and 1 fork, so there is limited community validation. Popularity is supporting evidence rather than a decisive health measure.

Repo toolingcaution

Composer build tooling is present, but no security scanning tools were detected. That weakens ongoing assurance, though it is less serious than the maintenance gap.