Audit History
azure-validate - 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, 07:43 PM | 3 confirmed | 0 | No capability change |
| v4 | Jul 8, 2026, 05:12 AM | 2 confirmed | 0 | Network access |
| v3 | Jul 6, 2026, 06:20 PM | 2 confirmed | 0 | Network access |
| v2 | Jun 30, 2026, 07:53 AM | 4 confirmed | 0 | External commandsFilesystem accessNetwork access |
| v1 | Feb 21, 2026, 08:39 AM | No confirmed findings | 0 | Baseline |
Jul 23, 2026, 07:43 PM
All 56 static findings are false positives caused by Markdown formatting, relative documentation links, expected Azure checks, or project-local plan paths. Semantic review found a critical authority injection, high-risk execution of repository-defined builds, and a medium-risk wildcard CORS workaround.
Confirmed security concerns (3)
Risk Factors
⚙️ External commands (24)
📁 Filesystem access (8)
🌐 Network access (2)
Jul 8, 2026, 05:12 AM
The static findings were reviewed in context. Most scanner hits are Markdown examples, relative documentation links, or project plan references rather than executable attacks. SKILL.md still contains authority-style prompt language and a mandatory deployment handoff, which create semantic marketplace risk.
Confirmed security concerns (2)
Risk Factors
⚙️ External commands (24)
📁 Filesystem access (8)
🌐 Network access (2)
Jul 6, 2026, 06:20 PM
Most static alerts are false positives from Markdown links, inline code formatting, and documented Azure validation commands. However, SKILL.md contains instruction-hierarchy override language and a mandatory deployment handoff that can manipulate downstream agents. Remove those directives before marketplace publication.
Confirmed security concerns (2)
Static false positives ignored (4)
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
📁 Filesystem access (6)
⚙️ External commands (11)
Jun 30, 2026, 07:53 AM
AI review confirms a critical prompt injection pattern in SKILL.md that claims authority over prior training. Most external command, filesystem, and network findings are expected Azure validation guidance or documentation links, but the injection language and forced deployment handoff make the skill unsafe to publish.
Confirmed security concerns (4)
Static false positives ignored (2)
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 (237)
📁 Filesystem access (12)
Detected Patterns
Feb 21, 2026, 08:39 AM
All static findings are false positives. The skill is legitimate Microsoft Azure deployment validation documentation. Scanner detected documentation examples in markdown code blocks (e.g., 'az version', 'az account show'), standard Azure config paths (.azure/plan.md), relative markdown links (../../policy-validation.md), and documentation URLs. This is an official Microsoft skill for Azure deployment validation.