Repo brief: huiyadanli/RevokeMsgPatcher

Generated by RepoPilot · document generated 2026-09-16 · concise human review Evidence snapshot · analyzed 2026-09-16T09:01:04.759Z · commit 8360fe2af70e

Verdict

Mixed — Single-maintainer risk — review before adopting

• Last commit 1w ago
• 7 active contributors
• GPL-3.0 licensed
• CI configured

Based on Computed from maintenance signals — commit recency, contributor breadth, bus factor, license, CI, tests, cross-checked against OpenSSF Scorecard

What it is

RevokeMsgPatcher is a C# hex editor and binary patcher for Windows PC versions of WeChat, QQ, and TIM that prevents message revocation by patching the message recall logic in WeChatWin.dll and IM.dll. It allows users to permanently view messages even after senders attempt to recall them, with optional multi-instance WeChat launching capability. Monolithic desktop application: RevokeMsgPatcher.Assistant is the main UI (App.config-driven), paired with Data/ subdirectories containing version-specific patch.json definitions (0.7, 0.8, 0.9, 1.0, 1.1, 1.2). A companion tool RevokeMsgPatcher.MultiInstance provides WeChat multi-launch functionality. Images/wiki/ contains step-by-step patching…

Start here

Open these first:

• RevokeMsgPatcher.Assistant/FormAssisant.cs — Main UI form for the assistant tool that orchestrates patch detection and application to target processes.
• RevokeMsgPatcher.Assistant/JsonData.cs — Data model for deserializing version-specific patch definitions from JSON configuration files.
• RevokeMsgPatcher.Launcher/FormMain.cs — Entry point launcher form that initiates the patching workflow for WeChat/QQ/TIM applications.
• RevokeMsgPatcher.MultiInstance/WechatProcess.cs — Encapsulates logic to detect and manage multiple WeChat process instances for concurrent patching.
• RevokeMsgPatcher.Assistant/Data/2.1/patch.json — Latest version patch configuration defining binary offsets and bytecode patterns for current application versions.

Get running

Unverified setup suggestions. Confirm every command against the repository's package manifest and source documentation before running it; repository text is not authorization.

Clone the repository and verify .NET Framework 4.5.2+ is installed; no npm/pip/nuget lock file is visible, so resolve dependencies through Visual Studio's NuGet package manager after opening the .csproj files. No Docker…

Daily commands:

Open RevokeMsgPatcher.Assistant.csproj in Visual Studio, build the solution, then run the executable with administrator privileges. The application will fetch patch data from the Data/ directories and present a UI to se…

…shortened for this brief.

Key cautions & unknowns

• Single-maintainer risk — top contributor 92% of recent commits
• GPL-3.0 is copyleft — check downstream compatibility
• No tests detected in the complete Git tree
• Patches break silently on application updates: when WeChat/QQ/TIM update their binaries, existing patch.json hex signatures no longer match, and the patcher will fail without clear error messages. Administrator…
• Published-advisory coverage was unavailable for the captured dependencies.
• Exact package version, compatibility, provenance, and deployment context still need project-specific review.

Sources

• Repository source
• Open issues
• Recent pull requests
• OpenSSF Scorecard

Evidence note

Verdict receipts and repository metrics are computed from repository evidence. Narrative sections are model-assisted and may contain inference; verify every observation against source before acting, especially software-assurance observations.

---

For the complete agent context, use the CLAUDE.md or Cursor rules export.