Audit History
swiftui-expert-skill - 9 audits
Version comparison
Capability and finding changes across audited versions, newest first.
| Version | Date | Result | Review items | Change vs previous |
|---|---|---|---|---|
| v9 Latest | Jul 24, 2026, 09:48 AM | No confirmed findings | 0 | No capability change |
| v8 | Jul 23, 2026, 09:44 AM | 1 confirmed | 0 | No capability change |
| v7 | Jul 17, 2026, 10:10 AM | No confirmed findings | 0 | No capability change |
| v6 | Jul 17, 2026, 10:10 AM | No confirmed findings | 0 | No capability change |
| v5 | Jul 17, 2026, 10:10 AM | No confirmed findings | 0 | Filesystem accessContains scripts |
| v4 | Jul 6, 2026, 02:50 AM | No confirmed findings | 0 | No capability change |
| v3 | Jul 6, 2026, 02:50 AM | No confirmed findings | 0 | Network accessExternal commands |
| v2 | Jun 28, 2026, 11:42 AM | No confirmed findings | 0 | External commandsNetwork access |
| v1 | Jan 31, 2026, 08:39 AM | No confirmed findings | 0 | Baseline |
Jul 24, 2026, 09:48 AM
All 280 static findings are false positives caused by documentation syntax, SwiftUI terminology, parser metadata, or the intended local xctrace workflow. The trace recorder uses argument vectors instead of a shell, redacts displayed launch environment values, and requires explicit confirmation before system-wide recording. No prompt injection, credential access, network exfiltration, or malicious intent was found.
Risk Factors
🌐 Network access (1)
⚙️ External commands (50)
📁 Filesystem access (5)
⚡ Contains scripts (1)
Jul 23, 2026, 09:44 AM
Static matches were predominantly lexical false positives from Markdown backticks, SwiftUI API names, XML identifiers, and fixed-argument xctrace subprocess calls. One semantic issue remains: the recorder prints environment arguments, which may expose secrets in logs or agent transcripts.
Confirmed security concerns (1)
Risk Factors
🌐 Network access (1)
⚙️ External commands (50)
📁 Filesystem access (5)
⚡ Contains scripts (1)
Jul 17, 2026, 10:10 AM
All 276 static findings were adjudicated as false positives. Most are documentation or identifier matches; the bundled scripts perform only the documented local Instruments workflow with argument-array subprocess calls. No prompt injection, credential access, data exfiltration, or command-injection intent was found.
Risk Factors
🌐 Network access (1)
⚙️ External commands (50)
📁 Filesystem access (5)
⚡ Contains scripts (1)
Jul 17, 2026, 10:10 AM
All 276 static findings were adjudicated as false positives. Most are documentation or identifier matches; the bundled scripts perform only the documented local Instruments workflow with argument-array subprocess calls. No prompt injection, credential access, data exfiltration, or command-injection intent was found.
Risk Factors
🌐 Network access (1)
⚙️ External commands (50)
📁 Filesystem access (5)
⚡ Contains scripts (1)
Jul 17, 2026, 10:10 AM
All 276 static findings were adjudicated as false positives. Most are documentation or identifier matches; the bundled scripts perform only the documented local Instruments workflow with argument-array subprocess calls. No prompt injection, credential access, data exfiltration, or command-injection intent was found.
Risk Factors
🌐 Network access (1)
⚙️ External commands (50)
📁 Filesystem access (5)
⚡ Contains scripts (1)
Jul 6, 2026, 02:50 AM
Static analysis flagged markdown backticks, SwiftUI UI terms, and one example URL. Review found these are documentation examples and references, with no executable scripts, shell commands, network calls, data exfiltration, or prompt injection.
Risk Factors
🌐 Network access (1)
⚙️ External commands (135)
Jul 6, 2026, 02:50 AM
Static analysis flagged markdown backticks, SwiftUI UI terms, and one example URL. Review found these are documentation examples and references, with no executable scripts, shell commands, network calls, data exfiltration, or prompt injection.
Risk Factors
🌐 Network access (1)
⚙️ External commands (135)
Jun 28, 2026, 11:42 AM
Static analysis reported many command, reconnaissance, network, and weak-crypto indicators, but review found they are SwiftUI documentation false positives. The skill contains markdown guidance and Swift examples, with no executable scripts, no command execution instructions, and no evidence of data exfiltration or prompt injection.
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.
Jan 31, 2026, 08:39 AM
All static findings are false positives. The 'Ruby/shell backtick execution' detections are markdown code block delimiters in documentation files. The 'weak cryptographic algorithm' and 'system reconnaissance' patterns are false positives from documentation text and file paths. No actual code execution, network calls, or prompt injection attempts exist. This is a pure documentation skill containing SwiftUI best practices and reference guides.
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.