jacksonit/cnsms

Release historydanger

Only three releases exist, with the latest published in May 2020 and none in the past 12 months. This long release gap is substantial abandonment evidence, despite the earlier two-week release interval.

Repo commit activitydanger

The repository has had zero commits and zero active maintainers in the past three months, consistent with the package having received no development since May 2020. This sharply weakens confidence in ongoing maintenance.

Maintainerscaution

One registry maintainer is responsible for publishing the package. That is a limited support base for an independently owned project and increases continuity risk when activity is already absent.

Project backingcaution

The registry namespace and repository owner match, but the owner is an individual rather than an organization. This confirms ownership alignment without providing organizational backing to offset the thin maintenance base.

Repo popularitycaution

The repository has no stars, forks, or watchers. Popularity is only supporting evidence, but these counts provide no external adoption signal to compensate for the long inactivity.