Ross ROSS = Recommend OSS · open-source software intelligence for agents

dotnet/Nerdbank.GitVersioning

Stamp your assemblies, packages and more with a unique version generated from a single, simple version.json file and include git commit IDs for non-official builds. observed · 2026-08-28

github.com/dotnet/Nerdbank.GitVersioning · homepage · C# · MIT (permissive) observed · 2026-08-28

Health v2 · maintenance only

93/100

  • Activity 99
  • Release rhythm 80
  • Longevity 100
How is this computed?

round(0.45*activity + 0.35*rhythm + 0.20*longevity); archived -> min(score, 10) — computed 2026-09-03. Adoption (stars, forks) is never an input.

  • gap_med: 35
  • age_days: 4126
  • days_rel: 56
  • days_push: 7
  • n_releases_24m: 8

Full methodology

Adoption not part of the score

1585 stars · 186 forks observed · 2026-08-28

What it is AI-extracted, prompt v1, taxonomy v1, 2026-08-30, confidence not recorded

A .NET library and CLI tool that generates unique, semver-compatible version numbers for assemblies and packages from a single version.json file, derived from git commit history. It integrates with MSBuild and NPM to automatically stamp builds and provides runtime access to version info via a generated ThisAssembly class.

Use cases

  • automatically version .NET assemblies from git history
  • generate unique semver versions for every commit without tags
  • stamp NuGet and npm packages with build versions
  • embed git commit IDs in non-official builds
  • backtrack from a computed version to its source git commit
  • make builds reproducible without depending on git tags or branch names

When to choose

  • you build .NET projects and want automatic, deterministic versioning from git
  • you need unique versions per commit for reproducible CI builds
  • you want version info available at runtime in your assemblies
  • you publish NuGet or npm packages and need consistent version stamping

When to avoid

  • your project is not .NET-based and you don't need the npm integration
  • you prefer tag-driven or branch-name-driven versioning schemes
  • you need a language-agnostic versioning solution outside MSBuild/gulp ecosystems

Facets

library · maturity active

build-tool version-control cli developer-tools developer-tools version-control cross-platform dotnet cli semantic-versioning msbuild nuget npm git version-stamping ci-cd build-reproducibility devops nodejs

2 sources

Member repositories

RepositoryRoleHealth v2
dotnet/Nerdbank.GitVersioningmain93

For agents

markdown · JSON · MCP: product_card(name="dotnet/Nerdbank.GitVersioning")

Data as of 2026-08-30T08:39:29.467469+00:00 · Report a problem