autofac/autofac

An addictive .NET IoC container

View on GitHub ↗Jump to charts ↓Open shareable report

Summary Information

Updated 6 minutes ago
Type:Library / SDKCategory(s):Core & Utility LibrariesLanguages & Runtimes
Added to GitGenius on September 14th, 2026
Created on January 22nd, 2014
Open Issues & Pull Requests: 6 (+0)
GitHub issues: Enabled
Number of forks: 847
Total Stargazers: 4,657 (+0)
Total Subscribers: 213 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 2.8 hours
Mean response time: 57.5 days
90th percentile: 47.4 hours
Tracked items: 44

Most active contributors

Sign in to see contributor activity.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 2
New in 7 days: 3
Closed in 7 days: 4
Avg open age: 449 days
Stale 30+ days: 1
Stale 90+ days: 0

Recent activity

Opened in 7 days: 3
Closed in 7 days: 4
Comments in 7 days: 8
Events in 7 days: 23

Top labels

  • bug (8)
  • enhancement (7)
  • help wanted (6)
  • pending-input (5)
  • wontfix (2)
  • duplicate (1)
  • invalid (1)
  • question (1)

Most active issues this week

Sign in to see which issues are moving.

Detailed Description

Autofac is an inversion of control container for Microsoft .NET that manages dependencies between classes so applications remain easy to change as they grow in size and complexity.

Autofac treats regular .NET classes as components and handles their dependency relationships through a registration and resolution pattern. Developers register components with a ContainerBuilder, then resolve services from a lifetime scope—either the container itself or a nested scope. This approach decouples classes from their dependencies, reducing tight coupling and making codebases more maintainable as they evolve.

Autofac suits any .NET project where managing dependencies becomes complex enough to benefit from centralized configuration. It works across .NET Framework and .NET Core applications. The project provides integration libraries for popular frameworks, available as separate packages, which streamline adoption in specific application contexts. The documentation site, API reference, and active discussion forums provide substantial learning resources for teams evaluating or implementing the tool.

The project maintains a steady stream of releases with documented changes available on GitHub. Development activity shows consistent engagement with community questions on Stack Overflow and the discussion forum. The team actively accepts contributions and provides clear guidance through a contribution document in the repository.