Tools and methods

The Model Trust Gate

Available

A seven-layer, fail-fast decision gate for deciding whether to trust a given AI model for a specific use, ending in a signed Model Trust Record. A methodology, not a product: it composes NIST AI RMF, ISO/IEC 42001, CSA AICM, and OWASP into one runnable, auditable decision, and weights the work by whether the model is a cloud API or a self-hosted open-weight file. Current release v0.2.2, backed by a coverage crosswalk, four worked runs, and a directional local red-team pilot.

L0 to L6 fail-fast gate - cheap governance checks first, expensive attack testing last
Model Trust Record - one model, one use, a scoped verdict with an expiry
Red-team harness - guardrail, model-choice, and compression tests on local models
AI GovernanceNISTISO 42001CSA AICMOWASPRed Team

EU AI Act Blueprint and Timeline

Available

The eu-ai-act-blueprint repo turns the high-risk obligations into 79 engineering controls, 73 tied to a specific article, worked through for a CV-screening system. The timeline page shows when each part of the Act applies, as set by Regulation 2024/1689 as amended by Regulation 2026/1744, with status badges and a 'You are here' marker, and points to the Commission's official timeline for guidance and standards as they land.

Blueprint - 79 controls, 73 mapped to a specific article of Regulation 2024/1689
Timeline page - application dates after the Digital Omnibus, status derived from the date
EU AI ActGRCComplianceGPAI

Secure-By-Design-Agentic

Available

A reference implementation of a secure-by-design AI agent with MCP tool integration. Every architectural decision is mapped to specific OWASP, NIST, or CSA controls. Defense-in-depth agent - Input guard, tool authorizer, output filter. Hardened MCP server - Path canonicalization, no shell=True, rate limiting. Validation suite - Threat model + manual red-team test cases

PythonLocal LLMsMCPOWASPNISTRed Team

AI Red Team Orchestrator

Available

A single-file, three-layer red-team pipeline for a local LLM and its MCP servers, run against open-weight models through Ollama. It uses Garak, Promptfoo and PyRIT plus a built-in MCP descriptor scan, and writes one report mapped to the OWASP LLM and MCP Top 10. v0.1.0 adds capability scoping: you declare what each tool may reach, and it reports the gaps its rules check for. Limits: the descriptor scan is static and never calls a tool, and Promptfoo's OWASP preset uses a hosted test-case generator, so without a Promptfoo login that step is skipped.

Layer 1 - Garak probes and a Promptfoo broad eval against the model
Layer 2 - Promptfoo OWASP LLM Top 10 preset and a built-in MCP descriptor scan, with optional capability scoping
Layer 3 - PyRIT multi-turn attacks (Crescendo, TAP), judged by the target model itself; a separate judge is on the roadmap
PythonLocal LLMsMCPOWASPNISTRed Team