Platform Evolution
Assessment run-2026-07-27-1 · 213 of 213 repos assessed
Repos / tc-audited-db-context

tc-audited-db-context

Tiny shared NuGet library (TC.AuditedDbContext) providing an Entity Framework 6 DbContext base class that stamps CreatedBy/LastModifiedBy audit fields on ITrackedEntity entities at SaveChanges.

50 · ambermediumlooseNo 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
FrameworksEntity Framework 6.2
Runtimes.NET Framework 4.6.2
Tests / CInone / CI in place
Last commit2019-03-14
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)
Releases2 release pipeline(s): tc-audited-db-context develop; tc-audited-db-context release
Integration-
SourceOpen in Azure DevOps

Risk flags

Each flag links to its glossary definition.

Dependencies in context

No internal dependencies, dependents or shared stores recorded for this repo.
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.
    Used by (0)
    No internal dependents.

    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

    Review tc-audited-db-context for retirement

    Dormant (last commit 2019-03-14) yet still release-linked, and nothing depends on it. Confirm remaining use, then retire and disarm its pipeline.

    Impact: Shrinks the estate before the expensive work begins

    proposed

    Assessment notes

    tc-audited-db-context

    Purpose

    A single-project class library publishing the TC.AuditedDbContext NuGet package: an abstract AuditedDbContext (EF6 DbContext) whose SaveChanges override sets CreatedBy/CreatedDate/LastModifiedBy/LastModifiedDate on any added or modified entity implementing ITrackedEntity, resolving the current user via TC.UserUtilities.MultiContextUser. Two source files in total.

    Tech stack

    C# SDK-style csproj targeting .NET Framework 4.6.2 with GeneratePackageOnBuild (version 1.0.5 via version.props). Depends on EntityFramework 6.2.0 and the internal TC.UserUtilities 1.0.1 package; restores from the internal Azure Artifacts feed per NuGet.config.

    Deployment

    Included as prod_application with 2 releases. Classic build and release pipelines (tc-audited-db-context develop / tc-audited-db-context release) — no YAML in the repo. The pipelines pack and publish the NuGet package.

    Dependencies

    Internal: TC.UserUtilities (maps to no included repo, so none listed as estate dependencies). External: none — the only third-party package is Entity Framework.

    Data stores

    None directly; it is an abstraction over SQL Server via EF6 for its consumers and holds no connection strings (the App.config only contains EF provider configuration).

    Integration points

    None; it is a pure library.

    Code health

    No tests, no README, no docs. Last commit 2019-03-14 — dormant for over seven years while still being deployed as a package. CI exists only as classic pipelines.

    Modernisation risks

    The library hard-couples consumers to EF6 on .NET Framework 4.6.2 (an end-of-life runtime) and to ambient user resolution via TC.UserUtilities; any consumer moving to EF Core / modern .NET must replace it (EF Core has interceptor-based equivalents). Its own risk of breakage is low given its size, but it is a legacy pin on every EF6 consumer in the estate — medium priority, best retired alongside its consumers' EF Core migrations.