silenceper/wechat

WeChat SDK for Go (微信SDK:简单、易用)

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 14 minutes ago
Added to GitGenius on September 12th, 2026
Created on September 6th, 2016
Open Issues & Pull Requests: 100 (+0)
GitHub issues: Enabled
Number of forks: 1,139
Total Stargazers: 5,298 (+0)
Total Subscribers: 121 (+0)

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 6
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 554 days
Stale 30+ days: 6
Stale 90+ days: 5

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 (10)
  • enhancement (10)
  • question (5)

Most active issues this week

No issue events were indexed in the last 7 days.

Detailed Description

wechat is a Go SDK that provides access to WeChat platform APIs.

The SDK addresses the need for Go developers to integrate with WeChat services without building API clients from scratch. It wraps WeChat's official APIs with Go-idiomatic interfaces, handling authentication, request formatting, and response parsing. The project is organized into modules covering different WeChat platforms: official accounts for public messaging, mini programs, mini games, payment processing, open platform functionality, enterprise WeChat, and AI speech capabilities.

Developers should choose this SDK if they are building Go applications that need to interact with any WeChat platform. It suits projects ranging from chatbots and customer service systems built on official accounts to e-commerce integrations using WeChat Pay or mini program backends. The README does not compare this SDK to alternatives, so no comparative guidance can be offered.

The project maintains active CI workflows validating Go compatibility. The codebase is organized into clearly separated modules by WeChat service type, making it straightforward to depend only on needed functionality. The project explicitly documents which APIs remain unimplemented and invites contributions through a structured process that references an API checklist, suggesting a methodical approach to expanding coverage.