microsoft / microsoft/msphpsql
[aw] Detection Runs
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 1.9k
- Forks
- 385
- Avg merge
- 3d 22h
- Merged PRs (30d)
- 1
Description
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.
What is a Detection Problem?
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.
How This Helps
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
Resources
[!TIP]
To configure threat detection behavior, update the frontmatter: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.
- expires on Jul 18, 2026, 4:51 AM UTC
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
This is an automatically managed detection-run tracker, not an implementation task. The issue states that no action should be taken and that it must not be assigned to an agent; there is no file, test, or change target to investigate.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, yaml
- Domain
- devops, security
- Issue type
- Bug
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 5/100