lowleveldesign/dotnet-wtrace

This system is a .NET-based command-line tool designed for analyzing .nettrace files and interpreting diagnostic events. It provides capabilities for filtering trace data, handling garbage collection, loader, and network events, and interpreting trace outputs. The tool has been modernized to target .NET 9, with updated dependencies and a simplified interface that no longer supports process ID or name filtering.

The PowerShell script 'Update-AssemblyInfoVersionFiles.ps1' has been removed from the repository. This script previously automated the update of assembly version numbers in .csproj files during the build process. Its removal indicates that this specific versioning mechanism is no longer required or has been replaced by another process.

scripts · high confidence

The dotnet-wtrace tool no longer supports filtering by process ID or name, as the corresponding filter types and parsing logic have been removed. The command-line interface now accepts a .nettrace file as an input source, allowing users to analyze pre-recorded traces. Additionally, the GC handler has been updated to safely handle missing or unexpected trace events by using TryPop operations and logging warnings instead of crashing, and the default set of enabled handlers has been expanded to include 'gc,loader,network' alongside the default set.

dotnet-wtrace · high confidence

The README has been completely rewritten to provide comprehensive documentation for the dotnet-wtrace command-line tool, covering installation, tracing targets, event filtering, and output interpretation. The solution file has been updated to target Visual Studio 17.13.

(repo-wide) · low confidence

Removed test cases for the event filter functionality, including the performance benchmark for the filter function and the parsing tests for 'pid \>= str' and 'pid \>= 10'.

dotnet-wtrace.tests · high confidence

The project has been upgraded to target .NET 9.0, replacing the previous .NET Core 3.1 target. This includes updating the test project's dependencies, specifically upgrading NUnit from version 3.13.1 to 4.3.2, FsUnit from 4.0.4 to 7.1.1, and Microsoft.NET.Test.Sdk from 16.9.1 to 17.14.1. Additionally, the main library's NuGet packages, including Microsoft.Diagnostics.NETCore.Client and Microsoft.Diagnostics.Tracing.TraceEvent, have been updated to their latest compatible versions.

(dependencies) · high confidence

Written by watchdog.canine.dev from the codebase's own history, inside the signed delivery this page is composed from.

• CAI 59 → 61 (+2.1)
• Rubric changed (rubric-2026.08.19 → rubric-2026.09.15) — scores are not directly comparable.

• Code Health 95 → 95 (+0.0)
• Architecture 100 → 100 (-0.2)
• Maturity 57 → 57 (+0.0)
• Readiness 52 → 50 (-1.7)
• Security 54 → 73 (+18.2)

• Duplicated block (10 lines × 2) (dotnet-wtrace/Events/GC.fs)
• Duplicated block (10 lines × 3) (dotnet-wtrace/Events/GC.fs)
• Duplicated block (12 lines × 2) (dotnet-wtrace/Events/GC.fs)
• Duplicated block (15 lines × 2) (dotnet-wtrace/Events/AspNetCore.fs)
• Duplicated block (6 lines × 3) (dotnet-wtrace/Events/Network.fs)
• Duplicated block (9 lines × 2) (dotnet-wtrace/Events/Loader.fs)
• High: security finding (details withheld)
• High: security finding (details withheld)
• High: security finding (details withheld)
• High: security finding (details withheld)
• High: security finding (details withheld)
• High: security finding (details withheld)
• High: security finding (details withheld)
• High: security finding (details withheld)
• High: security finding (details withheld)
• High: security finding (details withheld)
• No exposed public API
• Test reliability not included
• The 'Installation' section is not present in the visible text, so the required prerequisite steps (dotnet CLI version, .NET Core SDK) are missing from the guide. (README.md)
• The 'Start a new testapp process with some arguments' option is mentioned in the outline but not shown in the visible text, so it is unverifiable from the README. (README.md)
• …and 4 more

• Documentation: no installation or build instructions (README.md)
• Documentation: no usage examples (README.md)
• Duplicated block (10 lines × 2) (dotnet-wtrace/Events/GC.fs)
• Duplicated block (10 lines × 3) (dotnet-wtrace/Events/GC.fs)
• Duplicated block (14 lines × 2) (dotnet-wtrace/Events/GC.fs)
• Duplicated block (36–37 lines × 2) (dotnet-wtrace/Events/AspNetCore.fs)
• Duplicated block (5 lines × 3) (dotnet-wtrace/Events/AspNetCore.fs)
• Duplicated block (8 lines × 2) (dotnet-wtrace/Events/GC.fs)
• End-of-life runtime: .NET net9.0
• High: security finding (details withheld)
• High: security finding (details withheld)
• High: security finding (details withheld)
• High: security finding (details withheld)
• High: security finding (details withheld)
• High: security finding (details withheld)
• High: security finding (details withheld)
• High: security finding (details withheld)
• High: security finding (details withheld)
• High: security finding (details withheld)
• High: security finding (details withheld)
• …and 5 more

Written by watchdog.canine.dev from the codebase's own history, inside the signed delivery this page is composed from.

lowleveldesign/dotnet-wtrace was measured the same way every project in this corpus was: the same rubric, at a pinned commit, with the result published in full. Point a surveyor at a repository you know and see whether you agree with it.