khellang/scrutor

Assembly scanning and decoration extensions for Microsoft.Extensions.DependencyInjection

View on GitHub ↗Jump to charts ↓Open shareable report

Summary Information

Updated 42 minutes ago
Type:Library / SDKCategory(s):Backend FrameworksWeb Development
Added to GitGenius on September 16th, 2026
Created on November 14th, 2015
Open Issues & Pull Requests: 42 (+0)
GitHub issues: Enabled
Number of forks: 278
Total Stargazers: 4,343 (-1)
Total Subscribers: 62 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 27.2 hours
Mean response time: 67.4 days
90th percentile: 228.9 days
Tracked items: 41

Most active contributors

Sign in to see contributor activity.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 10
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 856 days
Stale 30+ days: 10
Stale 90+ days: 8

Recent activity

Opened in 7 days: 0
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 0

Top labels

  • Bug (3)
  • Breaking Change (1)
  • Improvement (1)

Most active issues this week

No issue events were indexed in the last 7 days.

Detailed Description

Scrutor is an assembly scanning and decoration extension for Microsoft.Extensions.DependencyInjection.

The tool solves the problem of verbose, repetitive service registration in dependency injection containers. Rather than manually registering each service one by one, Scrutor scans assemblies to automatically discover and register types based on conventions. It also provides decoration capabilities, allowing you to wrap services with cross-cutting concerns like logging, caching, or validation without modifying the original service implementations.

Scrutor suits projects using the Microsoft.Extensions.DependencyInjection container that want to reduce boilerplate registration code and apply consistent patterns across many services. It is particularly valuable in larger codebases where manual registration becomes unwieldy, and in scenarios where you need to apply decorators to multiple services following a common pattern. The tool integrates directly into the standard ASP.NET Core dependency injection pipeline, making it a natural fit for applications already using that ecosystem.

The project maintains a steady cadence of updates addressing user-reported issues and feature requests. Pull requests receive timely review and feedback from maintainers. The codebase shows active engagement with the community through issue discussions and incorporation of user suggestions into the tool's design.