GitHub
Discover AI assets in your GitHub repositories with the Airia Code Scanner.
Airia discovers AI assets living in your GitHub repositories: agent frameworks, model SDK usage, prompt files, workflow definitions, MCP server configurations, and hard-coded LLM keys or endpoints.
How GitHub discovery works
GitHub discovery is powered by the Airia Code Scanner, which runs as a GitHub Actions workflow inside your repositories. Each scan analyzes the repository's contents and reports its findings to your Airia tenant; every scanned repository (or pull request) then appears as a GitHub connection under Discover → Connections, with the discovered code-based agents in the inventory. There is no credential form to fill in on the Airia side: the scanner authenticates to Airia with an API key you store as a repository secret.
What the scanner detects
| Category | Indicators |
|---|---|
| Agent frameworks | CrewAI, LangGraph, LangChain, and similar framework usage and agent definitions |
| Model SDK usage | Imports and dependencies such as openai, anthropic, azure-ai, google-genai in requirements.txt, package.json, pom.xml, and similar |
| Prompt files | Standalone prompt assets and templates (*.prompt, prompts/ directories, system-prompt strings) |
| LLM keys and endpoints in config | Model API keys and endpoint URLs in .env, config files, or infrastructure-as-code (a security finding as well as an inventory signal) |
| Model artifacts | Model files and references (including hosted model references such as Hugging Face) |
| Workflow files | n8n workflow exports, LangGraph graph definitions, and similar agentic workflow files |
| MCP server configs | Model Context Protocol server manifests and client configurations (for example mcp.json) |
Customer-side setup steps
- In Airia, generate an API key for the scanner: top-right user menu → Settings → API
Keys → Generate Key. Name it something like
code-scanner, and copy the value (shown once). - In the GitHub repository (or organization), add two Actions secrets: the Airia API key, and your Airia API URL (both values come from your Airia environment).
- Add the Airia Code Scanner workflow file under
.github/workflows/(your Airia team provides the current workflow template). It runs the scanner container on pull requests or on demand and reports findings to Airia. - Trigger the workflow (open a pull request or run it manually from the Actions tab).
- In Airia, open Discover → Connections → GitHub: the scanned repository appears as a connection, and its discovered agents land in the inventory with their detected frameworks and model references.
Notes
- One connection appears per scanned repository/scan target; multiple repositories mean multiple connections (unlimited).
- Discovered code-based agents carry the detected model reference where the scanner can extract one; agents whose model is not declared in code show without a model.
- GitHub is the supported source for code scanning today. If your repositories live in Azure DevOps, see the Azure DevOps coverage page for the supported interim path.