Repo brief: HearthSim/Hearthstone-Deck-Tracker

Generated by RepoPilot · document generated 2026-09-15 · concise human review Evidence snapshot · analyzed 2026-09-15T01:08:39.892Z · commit e8732a07887f

Verdict

Mixed — Mixed signals — read the receipts

• Last commit 3d ago
• 6 active contributors
• 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

Hearthstone Deck Tracker is a Windows desktop application written in C# that automatically tracks your card hand, deck, and opponent's plays during live Hearthstone matches, displaying this information via an in-game overlay or separate windows. It also functions as a deck manager, enabling import from multiple deck-building websites, local storage beyond Hearthstone's 27-deck limit, and deck export back to the game client. The repo is structured as a monolithic C# WPF desktop application: Bootstrap/ contains the installer configuration, HDTTests/ holds all unit tests organized by feature domain (Battlegrounds, BoardDamage, DeckImporting, Hearthstone secrets, LogReader), and lib/ contains…

Start here

Open these first:

• HearthWatcher/ArenaWatcher.cs — Core game-state watcher that monitors Hearthstone log files for arena and constructed game events.
• HDTTests/Hearthstone/LogReadingTest.cs — Primary test suite validating log parsing logic that feeds the entire deck-tracking pipeline.
• Bootstrap/Bootstrap.csproj — Entry point and bootstrapping configuration for the desktop application initialization.
• HearthWatcher/BaconWatcher.cs — Game mode-specific watcher handling Battlegrounds/Bacon mode state transitions and card picks.
• HDTTests/Hearthstone/SecretTest.cs — Tests for secret detection and management logic critical to opponent play prediction.

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.

No package manager manifest (packages.config, .csproj dependency list, NuGet config) is visible in the provided file structure. To set up locally: (1) verify you have Windows Vista or higher and .NET Framework 4.5+ inst…

Daily commands:

No evidence of a dev server or runtime script in the provided data. The application is a compiled Windows executable distributed via installer (.msi). To run tests: open HDTTests.csproj in Visual Studio and run the test…

…shortened for this brief.

Key cautions & unknowns

• Concentrated ownership — top contributor handles 56% of recent commits
• No tests detected in the complete Git tree
• Scorecard: default branch unprotected (0/10)
• Game log file dependency: The tracker relies on parsing Hearthstone's live log files (location and format not specified in data); if Blizzard changes log output, parsing will break silently. **DLL dependency…
• License evidence is incomplete or ambiguous.
• 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.