jc_programs/jc_file_manager

Release historydanger

Only one release exists, published nearly seven years ago, with no releases in the last 12 months. This is strong evidence of an inactive package, though a stable utility can sometimes need few releases.

Repo commit activitydanger

There were zero commits and zero active maintainers in the last three months, consistent with a repository that has been inactive for nearly seven years. This materially increases abandonment risk.

Project backingcaution

The repository is owned by an individual user rather than an organization, so the single-package maintainer context offers limited visible institutional backing.

Repo popularitycaution

The repository has only 3 stars, 1 fork, and 1 watcher. Popularity is supporting evidence rather than a verdict, but these figures provide little evidence of a broad maintenance community.

Repo toolingcaution

Composer build tooling is present, but no security scanning tools were detected. That weakens maintenance and review hygiene, although it is not evidence of malicious behavior.