richlander

richlander / dotnet-inspect

Public

Tool to inspect .NET assets, like docker inspect.

100
3
100% credibility
Found Feb 04, 2026 at 66 stars -- GitGems finds repos before they trend. Get early access to the next one.
Sign Up Free
AI Analysis
C#
AI Summary

A command-line tool for examining .NET libraries and packages to view their contents, public features, safety issues, origins, and version differences.

How It Works

1
🔍 Discover the library checker

You hear about a handy tool that lets you peek inside software building blocks to see what's inside and if they're safe.

2
📥 Get it set up

With one quick command, you add the checker to your computer so it's always ready to use.

3
📦 Check a building block

You name a library you want to use, and it shows you details like what it does, recent updates, and any known issues.

4
🔬 Spot the details

You see the full picture—public features, safety checks, and even code examples—making everything crystal clear.

5
🛡️ Verify trustworthiness

Run a quick check to confirm the library comes from a reliable source with verifiable origins.

6
📈 Compare changes

Easily see what's new or different between library versions to pick the best one.

✅ Build with confidence

Now you know exactly what you're using, feeling secure and excited to create your project.

Sign up to see the full architecture

5 more

Sign Up Free

Star Growth

See how this repo grew from 66 to 100 stars Sign Up Free
Repurpose This Repo

Repurpose is a Pro feature

Generate ready-to-use prompts for X threads, LinkedIn posts, blog posts, YouTube scripts, and more -- with full repo context baked in.

Unlock Repurpose
AI-Generated Review

What is dotnet-inspect?

dotnet-inspect is a C# CLI tool that acts like `docker inspect` for .NET libraries and NuGet packages, pulling metadata, APIs, dependencies, vulnerabilities, and source provenance in seconds. Run `dotnet-inspect package System.Text.Json` for package details or `api JsonSerializer` for public surface tables; it handles local DLLs, platforms, diffs between versions, extension methods, and type searches. As a portable dotnet inspector, it downloads from NuGet or GitHub tool cache, works on Windows 11, and outputs JSON or markdown for scripting.

Why is it gaining traction?

It crushes fragmented tools like dotnet jb inspectcode by bundling everything—API shapes, breaking change diffs, implementer searches, and source-link audits—into one zero-config command. Developers love the fuzzy matching, verbosity levels, and LLM integration for feeding accurate .NET inspect code into prompts. No more manual DLL decompiles or version hunts; it's a dotnet dll inspector that just works across runtimes.

Who should use this?

.NET library authors auditing APIs before releases, backend devs tracing extension methods in massive deps like Microsoft.Extensions, or AI engineers building MCP inspector dotnet run workflows for code gen. Perfect for package maintainers spotting vulnerabilities or teams diffing upgrades without full builds.

Verdict

Grab it if you inspect .NET assets daily—installs as a global tool, solid README with examples, baseline tests for reliability. At 85 stars and 1.0% credibility, it's early but battle-tested for core use; watch for wider adoption.

(198 words)

Sign up to read the full AI review Sign Up Free

Similar repos coming soon.