Scrutor
Register services using assembly scanning and a fluent API.
Total Downloads
296.8M
296,805,793
Published
Mar 12, 2018
Latest stable version
Install
.NET CLI
dotnet add package Scrutor --version 2.2.2
Package Manager Console
Install-Package Scrutor -Version 2.2.2
PackageReference
<PackageReference Include="Scrutor" Version="2.2.2" />
Frameworks
Dependencies
Microsoft.Extensions.DependencyInjection.Abstractions
[1.1.0, )
.NETFramework4.5.1
Microsoft.Extensions.DependencyModel
[1.1.0, )
.NETFramework4.5.1
Microsoft.Extensions.DependencyInjection.Abstractions
[1.1.0, )
.NETStandard1.0
NETStandard.Library
[1.6.1, )
.NETStandard1.0
Microsoft.Extensions.DependencyInjection.Abstractions
[1.1.0, )
.NETStandard1.6
Microsoft.Extensions.DependencyModel
[1.1.0, )
.NETStandard1.6
NETStandard.Library
[1.6.1, )
.NETStandard1.6
Adoption guide
Teams staying on built-in DI while reducing manual registration boilerplate.
Why it appears in the guide: Extends Microsoft DI with assembly scanning and decorator registration helpers. Trade-off: Convention-based scanning should be constrained to avoid accidental or ambiguous registrations.
No SPDX license expression is published. Review the license text and your organisation's policy before redistribution.
Compatibility metadata lists 3 target frameworks; confirm the exact target used by your application.
How to read this guidance
Sources: published NuGet v3 registry metadata and explicit NuBrowse editorial guides. Refresh: package metadata is refreshed from NuGet when the page loads. Limit: this is not a security, legal or compatibility guarantee; validate the selected version in your project.
Useful next steps
Move from package metadata to a concrete selection or review workflow.