mrs4s/go-cqhttp

cqhttp的golang实现,轻量、原生跨平台.

View on GitHub ↗Jump to charts ↓Open shareable report

Summary Information

Updated 37 minutes ago
Added to GitGenius on September 5th, 2026
Created on July 22nd, 2020
Open Issues & Pull Requests: 314 (+0)
GitHub issues: Enabled
Number of forks: 1,576
Total Stargazers: 10,637 (+0)
Total Subscribers: 69 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 12.6 hours
Mean response time: 181.2 days
90th percentile: 1114.8 days
Tracked items: 18

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 9
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 875 days
Stale 30+ days: 8
Stale 90+ days: 7

Recent activity

Opened in 7 days: 0
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 0

Top labels

  • bug? (13)
  • feature request (6)
  • delay (1)
  • documentation (1)
  • enhancement (1)
  • needs decision (1)
  • wontfix (1)

Most active issues this week

No issue events were indexed in the last 7 days.

Detailed Description

go-cqhttp is a Golang native implementation of a QQ bot framework that provides OneBot protocol support for building QQ robot applications.

The tool solves the problem of creating QQ bots by implementing the OneBot standard protocol in Go, built on top of MiraiGo. It acts as a bridge between bot applications and QQ's messaging system, offering multiple communication interfaces including HTTP API, reverse HTTP POST, forward WebSocket, and reverse WebSocket connections. The framework handles QQ protocol implementation details internally, allowing developers to focus on bot logic rather than protocol complexity.

Developers building QQ bots should be aware that the project has announced it can no longer be actively maintained due to QQ's continuous updates to encryption schemes targeting protocol libraries. The README recommends that bot developers migrate to headless NTQQ projects instead.

The project shows signs of being in maintenance mode rather than active development, with the maintainers having publicly acknowledged their inability to continue supporting it due to external factors beyond their control. The codebase remains available and functional for existing deployments, but no ongoing feature development or protocol updates should be expected.