scan_linear
Scan Linear issues and comments to detect leaked secrets like API keys, tokens, and passwords. Returns redacted findings without modifying your data.
Instructions
Read Linear issues and comments to detect leaked secrets (API keys, tokens, passwords). Never modifies Linear — no issues or comments are written. Auth: requires a Linear personal API key (lin_api_...); set LINEAR_TOKEN env var or pass api_key directly. Side effects: a redacted scan report is uploaded to the n0s1 backend; set allow_secret_upload=True to also upload AES-encrypted secret values for AI validation. Returns redacted findings — raw secret values are never included in the output. Subject to Linear API rate limits.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| api_key | Yes | Linear personal API key (lin_api_...) (or set LINEAR_TOKEN env var) | |
| report_format | No | Output report format | n0s1 |
| show_matched_secret_on_logs | No | Include redacted secret snippets in logs (default: false) | |
| ai_analysis | No | Queue async AI credential validation after the scan (requires n0s1 Pro) | |
| n0s1_api_key | No | n0s1 API key; overrides the N0S1_TOKEN env var | |
| allow_secret_upload | No | Upload AES-encrypted secret values to the n0s1 backend for AI validation (default: false) | |
| report_uuid | No | UUID to assign to the scan report; overrides the auto-generated one |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| report_uuid | Yes | ||
| status | Yes | ||
| summary | Yes | ||
| findings | No | ||
| next_cursor | No | ||
| usage | Yes | ||
| ai_analysis_status | No |