garagon/Aguara Security Scanner
Scan AI agent skills and MCP servers for security threats — prompt injection, data exfiltration, tool shadowing, and more.
View on GitHubTrust Signals
- Scorecard Score
- not yet scored
- Maintenance Recency
- Stale
- License
- None
Inputs
| name | description | required | default |
|---|---|---|---|
| path | Path to scan | no | ./ |
| severity | Minimum severity to report: critical, high, medium, low, info | no | info |
| fail-on | Exit code 1 if findings at or above this severity (critical, high, medium, low) | no | "" |
| format | Output format: terminal, json, sarif, markdown | no | sarif |
| output | Output file path | no | aguara-results.sarif |
| verbose | Show rule descriptions and confidence scores | no | false |
| rules | Additional rules directory | no | "" |
| disable-rule | Rule IDs to disable (comma-separated) | no | "" |
| max-file-size | Maximum file size to scan (e.g. 50MB, 100MB) | no | "" |
| version | Aguara version to install (empty = latest). Must be a semver release tag like v0.14.4. | no | "" |
| upload-sarif | Upload SARIF results to GitHub Code Scanning | no | true |
| install-script-ref | Advanced: git ref (semver tag or 40-char SHA) to fetch install.sh from. Normal consumers should leave this blank; the action automatically uses its own pinned ref (e.g. v0.14.4 when you pin `uses: garagon/aguara@v0.14.4`). This input exists for self-testing scenarios where the action runs from `uses: ./` and needs to exercise install.sh from a specific commit. | no | "" |
Outputs
| name | description |
|---|---|
| findings-count | Number of findings detected |
| exit-code | Exit code from aguara scan |