Modular / Pluggable Scanner Architecture

[luigi-agosti]

Turn the current single Shield engine into a Scanner pipeline (type Scanner interface { Assess(text string) RiskResult }).
Keep the existing IDPI pattern matcher as the default scanner.
Add easy registration: shield.RegisterScanner(NewInvisibleTextScanner()), shield.RegisterScanner(NewSecretsScanner()), etc.
Users can do shield.WithScanners("idpi", "secrets", "toxicity").

Benefit → idpishield stops being “just IDPI” and becomes a real lightweight Go guardrail suite.

[luigi-agosti]

Another point of view if this is:

Explicit Multi-Layer Pipeline

• Formalize your scanners into the same 4-layer style:
• Heuristics (your current patterns)
• Vector similarity
• LLM judge (optional)
• Canary check

Users get a single RiskResult with per-layer breakdown.

[Chetnapadhi]

I'm working on this — planning to implement a Scanner interface with RegisterScanner() and ExtraScanners config field, keeping all existing scanners as built-ins while allowing external plugins. Zero new dependencies. Will send a list shortly.