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

tc-api-tools

Shared NuGet library suite (TC.ApiTools, plus Core/Cors/Diagnostics/Logging/Swagger packages) bundling standard API cross-cutting concerns — CORS for TC domains, exception middleware, health checks, Swagger and logging — for ASP.NET Core services across the estate.

87 · greenlowlooseNo signalZDD: not applicablelibrary

Health score

87

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
25
Runs on supported modern .NET
Legacy transport / 15
15
No legacy WCF or SOAP surface
Test posture / 15
8
Some tests, coverage is thin
Security hygiene / 15
15
No credentials found in source
Dangerous coupling / 15
9
12 dependents without good tests
Activity / 10
10
Actively maintained
Deployment hygiene / 5
5
CI in place
Health over time
2026-07-24 (run-2026-07-24-1): 872026-07-27 (run-2026-07-27-1): 87
No change since 2026-07-24 (87 to 87).

Facts

Languagescsharp
FrameworksASP.NET Core 8, ASP.NET Core 10
Runtimes.NET 8, .NET 10
Tests / CIsome / CI in place
Last commit2026-07-02
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): \commercial\tc-api-tools
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 (1)
    tc-exceptions

    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

    Raise the test floor on tc-api-tools

    12 systems depend on it and test coverage is thin. Chokepoints carry good tests before they are changed.

    Impact: De-risks change for 12 dependent systems

    proposed

    Assessment notes

    tc-api-tools

    Purpose

    Publishes six NuGet packages from one repo: TC.ApiTools (an opinionated WebApplication setup wrapping versioning, PhenixAuth, validation, Swagger, logging, health checks and exception middleware), plus the smaller TC.ApiTools.Core, .Cors (TC-domain origin matching), .Diagnostics (global exception handler, status-code pages, ping-exception handler), .Logging and .Swagger. Widely consumed — many estate APIs (phenix-insurance, phenix-selling-api, phenix-currency, phenix-itineraries, tc-api-gateway and more) reference TravelCounsellors.ApiTools/TC.ApiTools.*.

    Tech stack

    C# class libraries multi-targeting .NET 8 and .NET 10 (framework-conditional Asp.Versioning versions), .slnx solution with central package management, Nerdbank.GitVersioning (version.json), StyleCop/Sonar/SecurityCodeScan/NetAnalyzers rulesets. Bundles PhenixAuth.AspNetCore.AuthenticationScheme 7, Swashbuckle 10, FluentValidation auto-validation, WebApi.Logger and TC.Diagnostics health checks.

    Deployment

    Included as prod_application with 1 release (build pipeline tc-api-tools CI, release pipeline \commercial\tc-api-tools). YAML azure-pipelines.yml uses the shared InternalOSS/azure-pipelines-templates CI template on SDK 10.x, packing all six packages to the internal feed.

    Dependencies

    Internal: TC.Exceptions.WebApiClient.AspNetCore (tc-exceptions). Other bundled packages — PhenixAuth, WebApi.Logger, TC.Diagnostics.HealthChecks, Common.Messages — map to no included repo. No external services.

    Data stores

    None; it is a pure library.

    Integration points

    None directly — it configures REST/Swagger/JWT plumbing for its consumers but makes no calls itself.

    Code health

    Two xunit.v3 test projects (integration tests for the exception handler via TestHost, unit tests for origin matching and middleware extensions) — reasonable for the surface area. Modern build hygiene throughout. README is untouched boilerplate. Actively maintained (last commit 2026-07-02).

    Modernisation risks

    Low as a codebase — it targets .NET 8/10 and is well kept. The risk is structural: it has high fan-in as the standard API bootstrap for the estate, so breaking changes or its transitive pins (PhenixAuth, Swashbuckle, WebApi.Logger versions) ripple across dozens of services, and any service stuck below .NET 8 cannot consume current versions.