OSS Tanbou

declare type maps and centralize repetitive object-to-object mapping code in .NET applications

About these scores

OSS scale score is an unbounded metric that log-compresses and weights Stars, Watchers, Forks, and Contributors. Discovery score is the current OSS scale score minus the score at discovery. Update pace is commits in the last 30 days, growth momentum is the OSS scale score difference within the recent observation window, and OSS health is a 0–100 rating based on available recency, Community Health, and release data.

Stars
10,186
Primary language
C#
License
Not determined
Repository last updated
Sep 9, 2026
On this page

Overview

AutoMapper is a .NET object-to-object mapping library. It lets applications declare source-to-destination type maps with CreateMap and centralize repetitive property-assignment code used for DTOs and similar models.

Features and best fit

Based on official documentation; not hands-on tested · Content checked:

Key features

Declare type maps instead of repeating property assignments

CreateMap<Source, Destination>() defines a mapping and mapper.Map<Destination>(source) executes it.

Sources: [1]

Integrate with DI and extensibility points

It integrates with IServiceCollection and supports resolvers, converters, conditions, and mapping actions for specialized conversions.

Sources: [1]

Best fit

Fits repetitive mappings between structurally similar .NET models

It is most useful when applications have many DTO, API, or view-model transformations with largely corresponding members.

Sources: [1]

Before adoption

Validate mapping configuration during development

The README demonstrates AssertConfigurationIsValid() for development-time validation; complex conversions should also be covered by explicit tests.

Sources: [1]

Version 16 requires a licensing and license-key decision

LICENSE.md describes RPL 1.5 terms and points users who do not want to release their software under those terms to a commercial License Agreement. The README also documents license-key configuration, so organizational use should review the applicable path.

Sources: [2][1][3]

Official sources

  1. [1]AutoMapper v16.2.0 README(2026-10-03)
  2. [2]AutoMapper v16.2.0 LICENSE.md(2026-10-03)
  3. [3]AutoMapper v16.2.0 release(2026-10-03)
Supplemental curator note

AutoMapper can remove repetitive DTO mapping code, but complex business rules should not disappear into opaque mapping configuration. Version 16 adoption should also include license-key setup and a review of the applicable license path.

Try it in 3 steps

  1. 1

    Add AutoMapper 16.2.0 to a .NET project

    Pin the stable release in the target project and review the applicable licensing terms before use.

    dotnet add package AutoMapper --version 16.2.0
  2. 2

    Register the license key and type map

    Follow the README DI example to configure the license key and source-to-destination mapping.

    services.AddAutoMapper(cfg => { cfg.LicenseKey = "<LICENSE_KEY>"; cfg.CreateMap<Foo, FooDto>(); });
  3. 3

    Map an object to the destination type

    Execute the registered map. During development, also validate configuration with AssertConfigurationIsValid().

    var fooDto = mapper.Map<FooDto>(foo);
Check the official README

Growth

Growth trends · Last 30 days

10,186 Stars

Trend data is still being collected.

Development activity

Last 90 days · weekly

Commits (last 30 days)
9
Open PRs
2

Development activity is still being collected.

Built with

Categories and tags

Categories

GitHub data

GitHub dataView detailed GitHub data
Stars
10,186
Forks
2,400
Watchers
369
Open issues
12
Contributors
152
Owner type
Organization
Primary language
C#
License
Not determined
Repository last updated
Sep 9, 2026
Write a related article

Share a guide or use case for this OSS in Markdown. Articles are published after administrator approval.

Report incorrect information

Tell us if any listing information is incorrect or outdated.

After reading this page, do you know what to do next?