Audit History
azure-messaging - 5 audits
Version comparison
Capability and finding changes across audited versions, newest first.
| Version | Date | Result | Review items | Change vs previous |
|---|---|---|---|---|
| v5 Latest | Jul 23, 2026, 06:53 PM | 1 confirmed | 0 | No capability change |
| v4 | Jul 8, 2026, 09:21 AM | No confirmed findings | 0 | Network access |
| v3 | Jul 6, 2026, 07:14 PM | No confirmed findings | 0 | No capability change |
| v2 | Jun 30, 2026, 07:24 AM | 1 confirmed | 0 | External commandsNetwork access |
| v1 | Feb 22, 2026, 08:40 AM | No confirmed findings | 0 | Baseline |
Jul 23, 2026, 06:53 PM
All ten static findings are false positives caused by Markdown backticks around MCP tool names, operation names, and a path. No shell or Ruby execution is present in SKILL.md. The documented Azure MCP workflow can read cloud resource metadata and diagnostic logs, so users should apply least-privilege access.
Confirmed security concerns (1)
Risk Factors
⚙️ External commands (10)
Jul 8, 2026, 09:21 AM
All static findings are false positives caused by Markdown inline-code backticks in SKILL.md. I found no prompt injection, data exfiltration intent, or unsafe command execution instructions in the reviewed content.
Risk Factors
⚙️ External commands (10)
Jul 6, 2026, 07:14 PM
All 20 static findings were adjudicated as false positives. The network hits are placeholder Azure endpoints or user-directed diagnostic checks, and the external-command hits are Markdown references to MCP tools. No prompt injection, malicious intent, or hidden data exfiltration behavior was found.
Risk Factors
🌐 Network access (4)
⚙️ External commands (9)
Jun 30, 2026, 07:24 AM
Static analysis reported many command, network, browser storage, weak crypto, and reconnaissance patterns. Manual review found these are Markdown troubleshooting examples, Azure SDK identifiers, placeholder endpoints, and links to Microsoft or Azure documentation, not executable skill logic. No evidence found of malicious intent, prompt injection, credential exfiltration, or hidden code execution.
Confirmed security concerns (1)
Static false positives ignored (3)
These static matches were dismissed by semantic review or matched schema-only tokens, so they are shown for transparency but do not drive the quality score.
Risk Factors
⚙️ External commands (178)
🌐 Network access (36)
Feb 22, 2026, 08:40 AM
This is a Microsoft-official troubleshooting reference skill containing only documentation and example commands for debugging Azure Event Hubs and Service Bus SDK issues. All static findings are false positives: code fences (backticks) are markdown examples, URLs point to official Microsoft documentation, and diagnostic commands are standard troubleshooting tools. No executable code or malicious patterns detected.