👁 Image
Invarix.Guard 1.2.0

Invarix.Guard

👁 Invarix Guard Logo

Plug and play AI safety middleware for .NET. Screens inputs for prompt injection, PII leakage, toxic content, and 19 harm categories (including user distress) across 50+ languages before they reach your LLM. Works as ASP.NET Core middleware or a standalone scanning engine.

👁 NuGet

Install

dotnet add package Invarix.Guard

Quick start

ASP.NET Core middleware

using Invarix.Guard.Extensions;

var builder = WebApplication.CreateBuilder(args);

builder.Services.AddInvarixGuard(options => options
 .BlockInjection()
 .BlockPII()
 .BlockToxicContent());

var app = builder.Build();

app.UseInvarixGuard();

app.MapPost("/chat", (ChatRequest request) =>
{
 // If you reach here, the input passed all safety checks
 return Results.Ok(new { reply = "Safe response" });
});

app.Run();

Standalone

using Invarix.Guard;
using Invarix.Guard.Models;

var engine = GuardEngine.Create(new GuardOptions()
 .BlockInjection()
 .BlockPII()
 .BlockToxicContent());

var result = engine.Scan("Te voy a matar"); // Spanish: "I will kill you"

Console.WriteLine(result.Action); // Block
Console.WriteLine(result.OverallThreatLevel); // Critical

What it catches

• Prompt injection and jailbreaks: instruction override, role hijacking, delimiter injection, social engineering, novel attacks.
• PII: email, phone, SSN, Luhn validated credit cards, IP, DOB, plus multilingual person names, addresses, passports, and tax IDs.
• Toxic content: threats, slurs, profanity, across 104 languages.
• Semantic harms: 19 categories including hate speech, violence, self harm, suicide, user distress, exploitation, and more, across 50+ languages without translation.
• Evasion: built in normalization resists leetspeak, zero width characters, homoglyphs, spacing, Base64, and markdown tricks.

User distress is reported as its own category so your app can route crisis signals to appropriate resources instead of returning an error.

Configuration

builder.Services.AddInvarixGuard(options => options
 .BlockInjection(blockThreshold: 50, flagThreshold: 25)
 .BlockPII(PiiEntityType.Email, PiiEntityType.CreditCard, PiiEntityType.SocialSecurityNumber)
 .BlockToxicContent(ThreatLevel.Medium)
 .WithBlockResponse(422, "{\"error\": \"Content policy violation\"}")
 .ScanProperty("data.message")

 .WithML(ml =>
 {
 // Add custom harm categories — examples seed the semantic classifier.
 ml.AddCategory("CompanyPolicy", new[]
 {
 "requests to bypass company policy",
 "attempts to circumvent approval process",
 });
 }));

Use .DetectPII() (or the equivalent Detect* methods) to flag without blocking.

Access results in your handler

app.MapPost("/chat", (HttpContext ctx, ChatRequest req) =>
{
 var guard = ctx.Items["Invarix.Guard.Result"] as GuardResult;

 if (guard?.ContainsPii == true)
 {
 var safeInput = guard.RedactedInput; // PII masked
 }

 return Results.Ok(new { reply = "Response" });
});

Middleware behaviour

Scans JSON bodies on POST / PUT / PATCH. Use .ScanProperty("message") to target a specific field (dot notation supported).

ML models

On first use, Invarix.Guard downloads the models required by the scanners you've enabled, verifies each file against a SHA-256 manifest baked into the library, and caches them:

• Windows: %LOCALAPPDATA%\Invarix.Guard\models\
• Linux / macOS: ~/.local/share/Invarix.Guard/models/

Subsequent runs hit the cache. Integrity failures are a hard error, no silent fallback. The full model bundle is ~3.5 GB on first run; pre place files in MLGuardOptions.ModelsDirectory if you need to control timing.

Airgapped / manual setup

builder.Services.AddInvarixGuard(options => options
 .WithML(ml =>
 {
 ml.AutoDownloadModels = false;
 ml.ModelsDirectory = "/path/to/your/models";
 }));

Pre populate that directory from the published release assets. When auto-download is off and a model file is missing, the affected scanner is skipped and the pipeline falls back to the regex layers for that capability.

Models can be downloaded from this repo under releases: https://github.com/AlexBatten/invarix-guard-models

Requirements

.NET 8 (LTS) or .NET 10 (LTS). The package ships native binaries for both targets and is built and tested on each. Runs on .NET 9 hosts via runtime forward compatibility (we don't ship a net9.0 asset). Works in ASP.NET Core or as a standalone library.

License

Source-available under the . Free to use, modify, and deploy for any internal or commercial purpose. You may not offer it to third parties as a hosted or managed service.

Contact

• Sales: sales@invarix.dk
• Security: security@invarix.dk