dtforce/resman

Release historydanger

The last release was in December 2016, and there were no releases in the following 12 months of recorded history; this is nearly ten years without a new release and strongly raises abandonment risk.

Repo commit activitydanger

There were no commits or active maintainers in the last three months, consistent with the repository having been inactive for nearly ten years.

Repo popularitycaution

The repository has zero stars and forks and only two watchers, providing little evidence of a community that could sustain or support the package if its sole publisher stops maintaining it.

Repo toolingcaution

Composer is used for the build, which is appropriate, but no security scanning tooling was detected, leaving maintenance and vulnerability-detection practices less transparent.

Repository archivedcaution

The repository is not archived, which preserves a path for maintenance, but its last push was in January 2017 and does not offset the long inactivity shown elsewhere.