mos/cform

Release historydanger

The latest release was in October 2016, nearly 10 years ago, and there have been no releases in the last 12 months. The nine-release history shows an established package, but the long publishing gap is a substantial abandonment concern.

Repo commit activitydanger

The repository recorded no commits and no active maintainers in the last three months, consistent with the nearly 10-year release gap. No provided maintenance signal compensates for this lack of current activity.

Maintainerscaution

One registry maintainer is responsible for publishing the package. The repository owner is an individual rather than an organization, so there is no provided backing signal to offset the thin maintainer base.

Repo issue activitycaution

Eight issues remain open, with no issues or pull requests created, closed, or merged in the last month. This suggests unresolved maintenance demand and little current project response.

Security policycaution

The linked repository has no security policy. This is a transparency and vulnerability-reporting gap, although it is less important than the package's much older maintenance history.