Monitor the signatures of CS2 plugin game data against the current server binaries.
- Python 93.1%
- Shell 6.9%
| Filename | Latest commit message | Latest commit date |
|---|---|---|
fe3b323033
Drop propose_sigs.py, resig.py and lib_x86.py with their tests, the bin_prev snapshot step and the proposals.json output. The tracker issue now lists broken signatures only. |
||
| data | ||
| docs | ||
| reports | ||
| scripts | ||
| tests | ||
| .env.example | ||
| .gitignore | ||
| LICENSE | ||
| README.md | ||
CS2 Server Signatures Tracker
Did the last Counter-Strike 2 update break your plugins? This tracker re-downloads the CS2 dedicated-server binaries on every game update and checks each tracked plugin's signatures against them. Green means a signature still points at exactly one function in the binaries Valve ships right now.
Current status
✅ All 108 signature checks pass on CS2
1.41.9.2.Last checked October 23, 2026 at 03:50:02 GMT · 4 project(s) tracked
| Project | Health | Signatures | Linux | Windows | |
|---|---|---|---|---|---|
| CounterStrikeSharp |  | 72/72 | ✅ | ✅ | details → |
| cs2-retakes-allocator |  | 6/6 | ✅ | ✅ | details → |
| MatchZy |  | 12/12 | ✅ | ✅ | details → |
| WeaponPaints |  | 18/18 | ✅ | ✅ | details → |
▼ Run details
- CS2 build:
1.41.9.2 - Signatures: 108 ok, 0 ambiguous, 0 broken (0 not-yet-validated)
- Offsets: 42 ok, 0 stale, 0 without a reference
- Depot manifests: 5751660862748360256, 5491505037461703699
- Fragility over time: docs/stats.md
✅ unique match · ⚠️ ambiguous · ❌ broken · 🕓 still resolves, replaced upstream
- What the results mean, and what to do about them - for server owners, plus how to track your own plugin.
- Reference coverage gaps - tracked symbols the analysis cannot vouch for yet, updated every run.
- Setup, pipeline internals, notifications
- Signature fragility over time
Inspired by ianlucas/cs2-signatures; self-hosted on Forgejo. MIT licensed.