Sooner or later every .NET project leans on a DLL that nobody can explain. The package was abandoned three years ago and its repository is gone. The internal utility library was written by someone who has long since left the company. The vendor SDK ships with documentation that stops exactly where your question starts. The behaviour is wrong, or surprising, or simply undocumented — and the one thing that would settle it, the source, is the one thing you do not have.
You do not need it. A compiled .NET assembly carries a near-complete, recoverable description of what it does: IL plus rich metadata naming every type, method and field. Glass.NET reads that and reconstructs readable C#, turning "I have no idea what this dependency does" into "let me read the method and find out." It is free, and it is strictly static — it reads metadata and IL and reconstructs C#, and never executes the assembly it inspects.…