Audit History
dotnet-backend-patterns - 7 audits
Version comparison
Capability and finding changes across audited versions, newest first.
| Version | Date | Result | Review items | Change vs previous |
|---|---|---|---|---|
| v7 Latest | Jul 7, 2026, 07:39 AM | No confirmed findings | 0 | No capability change |
| v6 | Jul 7, 2026, 07:39 AM | No confirmed findings | 0 | External commandsFilesystem access |
| v5 | Jul 1, 2026, 12:18 AM | 1 confirmed | 0 | External commandsFilesystem access |
| v4 | Jan 17, 2026, 08:32 AM | No confirmed findings | 0 | No capability change |
| v3 | Jan 17, 2026, 08:32 AM | No confirmed findings | 0 | External commandsFilesystem access |
| v2 | Jan 4, 2026, 05:09 PM | No confirmed findings | 0 | No capability change |
| v1 | Jan 4, 2026, 05:09 PM | No confirmed findings | 0 | Baseline |
Jul 7, 2026, 07:39 AM
The audit found no confirmed security issues after manual adjudication. Static alerts are false positives caused by Markdown code fences, C# syntax, .NET prose, and educational database examples. No evidence found for prompt injection, malicious command execution, data exfiltration, or host reconnaissance.
Risk Factors
⚙️ External commands (24)
📁 Filesystem access (2)
Jul 7, 2026, 07:39 AM
The audit found no confirmed security issues after manual adjudication. Static alerts are false positives caused by Markdown code fences, C# syntax, .NET prose, and educational database examples. No evidence found for prompt injection, malicious command execution, data exfiltration, or host reconnaissance.
Risk Factors
⚙️ External commands (24)
📁 Filesystem access (2)
Jul 1, 2026, 12:18 AM
Static analysis reported many high-risk patterns, but review found Markdown code fences, C# examples, and ordinary .NET identifiers misclassified as shell execution, reconnaissance, or weak cryptography. No prompt injection, malware intent, credential exfiltration, install scripts, or hidden executable behavior was found. The only real caution is an intentionally unsafe SQL example that is clearly labeled as an anti-pattern and followed by a parameterized replacement.
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.
Detected Patterns
Jan 17, 2026, 08:32 AM
This is a pure documentation and code template skill containing only educational C#/.NET patterns. Static findings are 100% false positives caused by the scanner misidentifying: (1) markdown code fences as Ruby backticks, (2) SQL/database patterns as cryptographic terms, (3) standard C# namespace imports as reconnaissance. No executable code, network calls, file system access, or command execution exists. All content is static educational material.
Risk Factors
⚙️ External commands (85)
📁 Filesystem access (2)
Jan 17, 2026, 08:32 AM
This is a pure documentation and code template skill containing only educational C#/.NET patterns. Static findings are 100% false positives caused by the scanner misidentifying: (1) markdown code fences as Ruby backticks, (2) SQL/database patterns as cryptographic terms, (3) standard C# namespace imports as reconnaissance. No executable code, network calls, file system access, or command execution exists. All content is static educational material.
Risk Factors
⚙️ External commands (85)
📁 Filesystem access (2)
Jan 4, 2026, 05:09 PM
Pure documentation and code template skill. Contains no executable code, network calls, file system access, or command execution. All content is educational material with example C# patterns for .NET backend development.
Jan 4, 2026, 05:09 PM
Pure documentation and code template skill. Contains no executable code, network calls, file system access, or command execution. All content is educational material with example C# patterns for .NET backend development.