verzth/tcx-client

Release historydanger

The latest release was published about seven years ago, with no releases in the last 12 months and only two releases overall. That is strong evidence of abandonment risk for a package intended as a maintained dependency.

Repo commit activitydanger

The repository recorded no commits and no active maintainers in the last three months, consistent with the long release gap. This leaves little evidence of ongoing maintenance capacity.

Repo popularitycaution

The repository has zero stars and forks and only one watcher, providing little community visibility or backup support. Popularity is supporting evidence rather than decisive on its own, but it reinforces the maintenance concern.

Security policycaution

The repository has no security policy, so there is no documented process for reporting or handling vulnerabilities. This is a transparency and maintenance gap, though it is less serious than the inactivity.