getjump/vk

Release historydanger

The latest release was in October 2016, with no releases in the last 12 months. Nearly 10 years without a release is strong evidence of abandonment risk for a library dependency.

Repo commit activitydanger

There were no commits and no active maintainers in the last 3 months. Combined with the old registry release, this indicates very limited current maintenance.

Repo issue activitycaution

There were 11 open issues and 6 open pull requests, with no new or closed issues or pull requests in the last month. This suggests unresolved maintenance demand and weak recent responsiveness.

Security policycaution

The repository has no security policy. That is a transparency and vulnerability-reporting gap, though it is less serious than the lack of recent development.

Version stabilitycaution

Version 0.6.0 is not a stable major release, so compatibility expectations are weaker. This is secondary to the much older release history but still adds adoption risk.