GuardRails

• Verdict: Pass
• Confidence: High
• Analyzed: Feb 24, 2026, 8:34 AM
• Findings: 0
• Version: 1.0.2

Overview

The skill's code, instructions, and requirements are consistent with a local policy/guardrails engine; nothing requests unrelated credentials or installs arbitrary remote code.

This implementation is coherent with its stated purpose: it's a local policy/guardrails engine (FastAPI) that stores policies and audit logs in a database (defaults to a local SQLite file). Before installing or running: 1) Recognize it will create a database file (guardrails.db by default) and expose HTTP endpoints — restrict network access or put it behind auth in production. 2) If you set GUARDRAILS_DATABASE_URL to use a remote DB, ensure credentials are handled safely. 3) The /seed endpoint will insert many default policies; review them before seeding. 4) No external network calls or secret exfiltration were found, but always run third-party code in an isolated environment and review/configure access controls for the API in production.