[aw] Detection Runs

This issue tracks all runs where threat detection flagged problems in agentic workflows in this repository. Each workflow run that completes with a detection warning or failure posts a comment here.

<details>
<summary>What is a Detection Problem?</summary>

A detection problem occurs when the threat detection system either:
- **Detects potential security threats** (prompt injection, secret leak, malicious patch)
- **Fails to produce results** (agent failure, parse error)

When `continue-on-error: true` (the default), these problems produce warnings and safe outputs still proceed. When `continue-on-error: false`, they block safe outputs entirely.

</details>

<details>
<summary>How This Helps</summary>

This issue helps you:
- Track workflows where threat detection raised concerns
- Review patterns of detection warnings or failures
- Identify false positives or recurring issues with threat detection
- Monitor the health of the threat detection system

</details>

<details>
<summary>Resources</summary>

- [GitHub Agentic Workflows Documentation](https://github.com/github/gh-aw)

</details>

> [!TIP]
> To configure threat detection behavior, update the frontmatter:
> ```yaml
> safe-outputs:
>   threat-detection:
>     continue-on-error: true   # Warnings only (default)
>     # continue-on-error: false  # Strict mode — block safe outputs
> ```

---

> This issue is automatically managed by GitHub Agentic Workflows. Do not close this issue manually.
>
> **No action to take** - Do not assign to an agent.



> - [x] expires  on May 18, 2026, 11:20 PM UTC

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

[aw] Detection Runs #27100

Metadata

Assignees

Labels

Type

Fields

Projects

Milestone

Relationships

Development

[aw] Detection Runs #27100

Description

Metadata

Metadata

Assignees

Labels

Type

Fields

Projects

Milestone

Relationships

Development

Issue actions