Repo brief: pardeike/Harmony

Generated by RepoPilot · document generated 2026-09-15 · concise human review Evidence snapshot · analyzed 2026-09-15T05:37:08.874Z · commit 50896dd1512a

Verdict

Mixed — Single-maintainer risk — review before adopting

• Last commit 2d ago
• 9 active contributors
• MIT 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

Harmony is a runtime IL-code patching library for .NET and Mono applications that allows you to modify, replace, or decorate methods without touching files or replacing originals wholesale. It enables multiple independent patches to coexist on the same method and is used heavily in game modding (Rust, Rimworld, Subnautica) and enterprise testing (Microsoft, Google WPF unit tests). Core capability: inject prefix/postfix logic and IL transpilers into compiled methods at runtime. Shared project structure under Harmony/: Public APIs in Harmony/Public/ (Harmony.cs, HarmonyMethod.cs, Patch.cs), internal IL manipulation in Harmony/Internal/ (CodeTranspiler.cs, MethodCreator.cs, Emitter.cs),…

Start here

Open these first:

• Harmony/Public/Harmony.cs — Main API entry point exposing the Harmony patching interface; every user interacts with this facade.
• Harmony/Public/PatchProcessor.cs — Core orchestrator that applies, removes, and manages patches; implements the central patching workflow.
• Harmony/Internal/MethodCreator.cs — Generates patched method IL code dynamically; critical to runtime method replacement implementation.
• Harmony/Internal/CodeTranspiler.cs — Transforms IL instructions during transpilation; enables user-level IL code manipulation.
• Harmony/Public/PatchClassProcessor.cs — Parses and processes attribute-decorated patch classes; bridges declarative and imperative patching APIs.

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: git clone https://github.com/pardeike/Harmony.git. The project uses .NET (evidenced by .csproj structure and Directory.Build.props). Build with: dotnet build Harmony.sln (verify .NET SDK version in Directory.…

Daily commands:

No dev server or runtime binary needed. This is a library: compile via dotnet build Harmony.sln, then reference the built assembly (Harmony/bin/Debug or /Release) or install NuGet packages Lib.Harmony or Lib.Harmony.T…

…shortened for this brief.

Key cautions & unknowns

• Single-maintainer risk — top contributor 81% of recent commits
• No tests detected in the complete Git tree
• Scorecard: default branch unprotected (0/10)
• IL expertise required: Modifying Emitter.cs or CodeTranspiler.cs demands deep CIL knowledge; mistakes silently corrupt method bytecode at runtime. Mono.Cecil dependency volatility: ForwardingAttributes exists…
• 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.