comsave/sdk

Release historydanger

The latest release was about six years ago, with no releases in the last 12 months. This strongly raises abandonment risk despite five releases arriving during the package's initial three weeks.

Repo commit activitydanger

The repository recorded zero commits and zero active maintainers in the last three months, consistent with the last push being about six years ago. This is strong evidence that maintenance has stopped.

Repo popularitycaution

The repository has zero stars and forks and only two watchers. Popularity is supporting evidence rather than a verdict, but these counters provide little evidence of an active user or contributor community.

Security policycaution

The repository has no security policy, leaving vulnerability reporting and response expectations undocumented. The lack of recent maintenance makes this gap more consequential.