AsmResolver
v6.0.1 open-sourceThe section your link pointed to isn't on AsmResolver's page any more, so we've brought you to the top.
AsmResolver is a library for reading, modifying, and reconstructing Portable Executable files, supporting native Windows and managed .NET images.
var peFile = PEImage.FromFile("app.dll");
var r2rSegment = peFile.ReadyToRun;
if (r2rSegment != null) {
var nativeCode = r2rSegment.NativeCode;
// Read or locate specific method bodies...
}
var stream = new BinaryStreamReader(data);
int remaining = stream.RemainingLength;
var member = module.LookupMember<MethodDefinition>("MyMethod");
if (member == null) {
var success = module.TryLookupMember<MethodDefinition>("MyMethod", out var found);
}
bool isModuleType = myTypeDefinition.IsModuleType;
public class MyClonerListener : IMemberClonerListener { public void MemberCloned(IMember original, IMember clone, ModuleBuilder builder) { builder.Modules[0].MetaDataRoot.MetadataTables.Add(clone); } }
bool areEqual = SignatureComparer.Default.Equals(sig1, sig2);
var genericMethod = type.MakeGenericInstanceMethod(arg1, arg2);
var body = method.Body ?? new UnresolvedMethodBody();
Summary
AsmResolver is an open-source library, released under the MIT license, that .NET programmers import into their own code to read, modify and rebuild Portable Executable files, including both native Windows images and .NET assemblies. It gives low-level access to sections, data directories and the Import Address Table alongside a higher-level API modeled on System.Reflection, and it is built to tolerate malformed or obfuscated binaries, which points it at reverse engineers and malware analysts and tool builders doing binary patching or instrumentation rather than at application developers shipping product code. It runs cross-platform across .NET Framework, .NET Core, Mono and .NET standard, and can read PDBPDBA debug symbol file format used by Microsoft's toolchain that maps compiled binaries back to source code, function names, and variable types, letting cyber tools resolve symbols during reverse engineering or memory analysis. and PortablePdb symbols without a DIA dependency. First committed in 2013, it now has 48 contributors and remains active, with 215 commits and a release cut 27 days ago.
AsmResolver is a library for reading, modifying, and reconstructing Portable Executable files, supporting native Windows and managed .NET images.
How AsmResolver helps
What does a suspicious binary actually import, and can the packed IAT be trusted?
walks the Import Address Table and reconstructs it directly from the PE structures, even when the file is packed or obfuscated, instead of trusting whatever the loader would resolve at runtime
Which symbol belongs to which address when all I have is a PDB next to the binary?
reads PDB and PortablePdb symbol streams itself, with no DIA dependency, so the mapping works the same on Windows, Linux or macOS
Will this file even parse, given how mangled the headers look?
is built to tolerate malformed or obfuscated structures rather than reject them, so a binary that trips up other tooling can still be walked and dissected
Does this executable carry a single-file bundle or a ReadyToRun image I need to unpack first?
recognizes AppHost/SingleFileHost bundles and R2R binaries directly, so their inner structures are reachable without a separate extraction step
Languages
Command line
| option | found in | since | description |
|---|
Values are placeholders taken from each option’s declared default. Nothing is executed here — the output shown is a recording of a run that already happened.
Score card
-
Shipping velocity releases a month, last 12 months
-
Documentation quality release-notes rubric, 0–100
-
Breaking-change discipline how rarely a release breaks users, and notice given
-
Maintenance risk quiet time against its own cadence, maintainers
-
Innovation & surface new capabilities, API and MCP surface
- Community health
-
Contributor trend distinct committers, this year against last
-
Maintainer concentration bus factor now against a year ago
-
Issue backlog trend issues closed per issue opened, 12 months
-
Responsiveness median time to a maintainer’s first reply
Nine scores for AsmResolver, each built from the releases, notes and API history this site tracks — and, on Researcher and Business, where it stands among every measured tool in its category and how that has moved.
Score cards are part of every paid plan.
See plans → Already subscribed? Sign in →Trajectory
Blank means never measured; nothing here is a filled-in zero.
Peer standings are included with Researcher and Business. See how this tool ranks against its competitors, using data we don't publish anywhere else.
See plans →Each score is 0–100 on a published rubric, derived from data this site already shows. A dimension we cannot measure says so — it is never scored 0 and never enters a rank.
How this is scored
- Shipping velocity — releases a month over the last 12 months, on a log scale where 16 a month scores 100. Needs 3 releases in the window.
- Documentation quality — the release-notes rubric published on the analytics page, unchanged.
- Breaking-change discipline — the share of releases carrying a breaking change (none scores 100, half or more scores 0). Only projects that label breaking changes are measured: a clean record cannot be told from an unlabelled one.
- Maintenance risk — quiet time measured against the tool's own release cadence (quiet longer than 90 days and three typical gaps scores 0), plus the number of active maintainers and whether contributors are growing, where known. Higher is lower risk.
- Innovation & surface — new capabilities in the feature ledger this year, API and MCP operations added, and the share of commits that are features: the mean of whichever we hold.
- Community health (open-source tools only) — each is a direction, not a size: contributors this year against last, the bus factor now against a year ago, and issues closed per issue opened, where steady scores 50, doubled 100 and halved 0; plus the median time to a maintainer's first reply (an hour scores about 100, a month or more 0). A commercial card has no repository and carries none of the four.
- Documented delivery (commercial tools) — when a vendor's documented new capabilities have slowed against its own baseline, that counts against the overall standing as heavily as two low dimensions. Steady delivery, or too little history to judge, leaves the standing alone; it is never a sixth score.
- Open-source tools are scored on repository signals; commercial tools on their published changelog. Ranks compare tools within one category and one profile and need at least five measured peers; the overall standing needs three ranked dimensions. Best-in-breed or consolidator is a shape, not a quality, and is never scored.
Release-note detail over time
See how much detail AsmResolver puts in its release notes, quarter by quarter, and compare it with tracked tools in the same category. This history uses up to ten retained, reviewed notes per tool; sparse or blank older quarters may reflect that limit.
Checking release-note history…
Releases
16 entries
No entries match these filters.
- July 20261
- May 20261
- February 20241
- November 20231
- July 20231
- May 20231
- March 20231
- January 20231
- December 20221
- May 20221
- April 20221
- March 20221
- December 20211
- October 20211
- May 20211
- March 20211
Project health
Issue, contributor and maintainer activity in Washi1337/AsmResolver, 2023-10 – 2026-09, as of 2026-09-25. Twelve-month figures first; the trend lines run the whole window.
- Contributors 12 +3 vs prior 12 months
- Maintainers 3 +3 joined · −3 left, last 12 months
- Bus factor 1 committers behind half the commits
- Community-filed 88% of issues opened, last 12 months
- Median time to close 38 days first maintainer reply 2.3 days
- Open backlog 13 of 261 issues ever filed
- Issues opened / month 0 · 0 communitymaintainers
- Open backlog 13
- Contributors / month 0
- Commits / month 0
- Stars 1,119
- bugs 63%
- features 6%
- questions 19%
- other 12%
Counts from the project's public repository and git history; no individuals are identified. Maintainers are the committers covering 80% of the last year's commits. how we measure this
Libraries its release ships
What its latest release locks, checked against known advisories.None of its release's images build from a lockfile we can read.
Add the badge to your README
Maintain this project? The badge links readers straight to this page, so they can follow every release here.
Choose a badge style and copy the code →