Platform Evolution
Assessment run-2026-07-27-1 · 213 of 213 repos assessed
Repos / tc-swagger-versioning

tc-swagger-versioning

Retired NuGet library (TC.Swagger.Versioning) of convenience extensions that wire up API versioning and Swashbuckle Swagger with XML comments in ASP.NET Core Web APIs; superseded by tc-api-tools.

50 · amberlowlooseNo signalZDD: not applicablelibrarydormant

Health score

50

0 to 100 across seven weighted factors; nothing is hidden. Green is 75 and above, amber 50 to 74, red below 50. How scoring works.

Runtime currency / 25
0
.NET Framework, out of mainstream support
Legacy transport / 15
15
No legacy WCF or SOAP surface
Test posture / 15
0
No tests
Security hygiene / 15
15
No credentials found in source
Dangerous coupling / 15
15
No dangerous coupling detected
Activity / 10
0
Dormant: no meaningful change for two years or more while still deployed
Deployment hygiene / 5
5
CI in place
Health over time
2026-07-24 (run-2026-07-24-1): 502026-07-27 (run-2026-07-27-1): 50
No change since 2026-07-24 (50 to 50).

Facts

Languagescsharp
FrameworksSwashbuckle.AspNetCore 4, ASP.NET Core 2.1
Runtimes.NET Standard 2.0, .NET Framework 4.6.1
Tests / CInone / CI in place
Last commit2019-08-16
OwnerOwner unknown (mapping to be curated)
DomainPlatform services (system generated; curate in repo-owners.json to override)
Product areaShared platform
HostedNo signal No hosting signal in its pipelines (typical for libraries and contract packages)
Releases1 release pipeline(s): tc-swagger-versioning master
Integration-
SourceOpen in Azure DevOps

Risk flags

Each flag links to its glossary definition.

Dependencies in context

Laying out the graph…
greenamberreddata store (square, dashed link)Node size follows fan-in. Click any node to open it.

Entanglement

loose No binding mechanisms apply: this system needs no untangling work.

    Depends on / used by

    Depends on (0)
    Nothing internal.

    Migration playbooks

    Generated from this repo's assessment data: what is feasible, what blocks it, and the steps in order. Ratings: green means actionable now, amber means sequence other work first, red means blocked, grey means not applicable.

    ZDD adoption

    Not applicable

    Not a deployed service (libraries, database definitions, desktop apps) or a retirement candidate not worth the investment. Ships as a package; ZDD applies to the services that consume it.

    SQL Server exit

    Not applicable

    No SQL Server dependency is recorded for this repo. Nothing to migrate.

    Containerisation

    Not applicable

    Libraries ship as packages, not as running services. There is nothing to containerise.

    Recommended actions

    Replatform tc-swagger-versioning to modern .NET

    Runs on .NET Standard 2.0, .NET Framework 4.6.1, out of mainstream support. No pinning dependency blocks it; sequence by fan-in (providers before consumers).

    Impact: Unblocks 2 dependent system(s)

    proposed

    Assessment notes

    tc-swagger-versioning

    Purpose

    A tiny two-class library publishing the TC.Swagger.Versioning NuGet package: StartupExtensions (AddVersioning / AddSwaggerWithXmlComments / UseSwaggerWithBaseUrl convenience methods) and a SwaggerDefaultValues operation filter. A checked-in RETIRED.md states it has been retired and merged into the tc-api-tools repo under the TravelCounsellors.ApiTools namespace.

    Tech stack

    C# class library multi-targeting netstandard2.0 and net461, version 1.1.3 with GeneratePackageOnBuild. Pinned to 2018-era dependencies: Microsoft.AspNetCore.Mvc 2.1, Mvc.Versioning 3.x, Swashbuckle.AspNetCore 4.0 (uses the removed Info/DescribeAllEnumsAsStrings APIs, so it cannot compile against Swashbuckle 5+).

    Deployment

    Included with 1 release: classic build pipeline tc-swagger-versioning master and matching release pipeline of the same name (no YAML in the repo). A PreBuildScripts/UpdateNugetVersion.ps1 supports the classic build. "Deployment" is NuGet package publication rather than a running service.

    Dependencies

    No internal estate packages; external dependencies are only the Microsoft/Swashbuckle framework packages listed in the csproj. Nothing at runtime beyond its consumers.

    Data stores

    None — pure library.

    Integration points

    None directly; it configures Swagger/versioning for consuming APIs.

    Code health

    No test projects at all. Boilerplate README; the only meaningful documentation is RETIRED.md. Dormant since 2019-08-16.

    Modernisation risks

    Formally retired: the correct action is confirming no consumer still references TC.Swagger.Versioning, then removing the build/release pipelines and archiving the repo. Its inclusion in the deployed list suggests the pipeline linkage outlived the library. Any remaining consumers are pinned to Swashbuckle 4/ASP.NET Core 2.1 and should move to tc-api-tools.