48
/ 100
The fundamentals need work — start with test coverage and setup instructions.
:trollface: A hex editor for WeChat/QQ/TIM - PC版微信/QQ/TIM防撤回补丁（我已经看到了，撤回也没用了）
A low grade is a to-do list, not a judgment of your code
Most gaps here are documentation, tests, and setup, not the code itself. Closing your top 3 gaps alone would lift this repo to C (74).
See your top fixesTop fixes
Highest-impact changes first, ranked by point weight
- 1Tests18pt
Add automated tests. They prove the code works and give contributors confidence to make changes.
- 2CI/CD14pt
Add a step like `run: npm test`, `run: pytest`, or `run: tox` to your workflow file.
- 3CI/CD14pt
Add a lint step to catch style issues automatically.
- 4CI/CD14pt
Add `tsc --noEmit`, `mypy`, or `cargo check` to catch type errors before they merge.
Working through the fixes? Let every push regrade itself.
The free GitHub App rescans this repo on every push and posts the grade as a commit check, so the score climbs without coming back to rescan by hand.
Scorecard
Every check, grouped by category and sorted worst-first
Documentation
51
No install instructions found in the README (−45 pts).
→ Add a section showing how to install dependencies.
No CONTRIBUTING.md found (−47 pts base + up to −53 pts more for content).
→ Add a CONTRIBUTING.md telling newcomers how to get involved. Include setup, code style, test, and PR instructions.
README is present.
Licensed under GPL-3.0.
Engineering
29
No tests detected anywhere in the repository.
→ Add automated tests. They prove the code works and give contributors confidence to make changes.
No .NET formatter configured.
→ Add an .editorconfig to define C# formatting rules and run `dotnet format` in CI.
No dependency lockfile found (−70 pts).
→ Enable and commit packages.lock.json so NuGet restores are repeatable.
CI is configured (.github/workflows/build.yml).
Issue or PR templates present.
Project health
95
Actively maintained (pushed within 3 months).
Dependency manifest found (RevokeMsgPatcher.sln).
Repository has a description.
.gitignore present.
Repository health signals
Activity, community, and responsiveness at scan time
Activity
- 0 / 7Commits (30d / 90d)
- 4,064Forks
- 21Releaseslatest 5y ago
Community
- 42% - WeakCommunity health
- 1 bus factorlowauthor own >50% of commits
- 38,782Watchers
Responsiveness
- 4hMedian issue response
- <1hMedian PR merge time
- 58Open issues
Repository files11 root entries
- .githubGood: CI is configured (.github/workflows/build.yml).Good: Issue or PR templates present.
- Images
- RevokeMsgPatcher
- RevokeMsgPatcher.Assistant
- RevokeMsgPatcher.Launcher
- RevokeMsgPatcher.MultiInstance
- .gitignoreGood: .gitignore present.
- appveyor.yml
- LICENSEGood: Licensed under GPL-3.0.
- README.mdGood: README is present.Good: README is well structured with multiple sections.Good: README includes screenshots or visuals. Great for first impressions.Issue: README has no code examples (−15 pts).Fix: Show a quick-start snippet so contributors can see what using your project looks like.Good: README links to a live demo or deployed app.Good: README includes status badges.Issue: No install instructions found in the README (−45 pts).Fix: Add a section showing how to install dependencies.Issue: No run or usage instructions found (−45 pts).Fix: Add a section showing how to start or use the project.
- RevokeMsgPatcher.slnGood: Dependency manifest found (RevokeMsgPatcher.sln).
Add this badge to your README
It updates automatically each time the repo is re-graded.
[](https://www.repo-grade.com/report/huiyadanli/revokemsgpatcher)