napneko/napcatqq

Modern protocol-side framework based on NTQQ

View on GitHub ↗Jump to charts ↓Open shareable report

Summary Information

Updated 48 minutes ago
Added to GitGenius on September 5th, 2026
Created on March 26th, 2024
Open Issues & Pull Requests: 28 (+0)
GitHub issues: Enabled
Number of forks: 818
Total Stargazers: 10,514 (+1)
Total Subscribers: 35 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 2.6 hours
Mean response time: 37.4 hours
90th percentile: 3.4 days
Tracked items: 982

How this project is maintained

Around half of the issues opened in the past year never receive a reply. Only 16% of issues opened in the past year have been closed. Three people close 85% of everything that gets resolved.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 18
New in 7 days: 3
Closed in 7 days: 0
Avg open age: 24 days
Stale 30+ days: 4
Stale 90+ days: 0

Recent activity

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

Top labels

  • bug (574)
  • enhancement (105)
  • invalid (36)
  • bug? (27)
  • suspend (19)
  • question (18)
  • good first issue (9)
  • help wanted (7)

Detailed Description

NapCat is a modern protocol-side framework that implements a QQ bot interface based on NTQQ.

The tool solves the problem of creating QQ bots by providing a protocol implementation that bridges NTQQ with bot frameworks. It works by exposing a complete API interface that allows developers to build bots without needing to understand the underlying NTQQ protocol details. The framework is designed to be lightweight enough to run on low-memory systems while maintaining stability through continuous development.

Developers should choose this tool if they need to build QQ bots and want an implementation that prioritizes ease of use and efficiency. It suits projects where memory constraints matter and where developers want a straightforward integration with standard bot protocols. The README notes that SnowLuma is offered as an alternative GUI replacement, though it does not make detailed comparisons with other protocol implementations.

The project maintains active community engagement through multiple documentation mirrors and QQ group channels, though it explicitly states that the community does not provide support for basic integration questions or framework-level issues. Development appears focused on stability and API completeness, with the tool claiming to implement most standard interfaces. The project is non-profit and expects users to have foundational programming skills before seeking community assistance.