codememory/support

Release historydanger

The latest release was about five years ago, with no releases in the last 12 months. Although the package had four releases in its first month, the long silence is a substantial abandonment concern.

Repo commit activitydanger

There were no commits and no active maintainers in the last three months. Combined with the old last push and release history, this strongly increases abandonment risk.

Maintainerscaution

Only one registry publishing account is listed. The repository is user-owned rather than organization-backed, so there is little visible publishing redundancy if that maintainer stops responding.

Package scaffoldingcaution

The package includes a README and has a GitHub release for this version. The nine-character README is minimal, while the absence of tests and a changelog is not a packaging defect by itself.

Project backingcaution

The registry namespace and repository owner are aligned, but both identify an individual user rather than an organization. This supports package identity while offering limited evidence of institutional backing.