fclone

Release historydanger

The package has 11 releases, but its latest release was in January 2017 and there have been no releases in the last 12 months. This is a substantial maintenance concern, although the linked repository remained available afterward.

Repo commit activitydanger

There were no commits and no active maintainers in the last three months. Combined with the old registry release, this indicates weak current maintenance capacity.

Maintainerscaution

Only one registry account has publish access, leaving a thin publishing base. This is partly consistent with the repository being owned by an individual, but it still increases continuity risk.

Project backingcaution

The repository is owned by an individual user rather than an organization, so there is no visible organizational backing to offset the thin maintainer base.

Repo issue activitycaution

The repository has one open issue and three open pull requests, with no issues or pull requests newly created or merged in the last month. This supports the view that current maintenance is limited.