Historique des audits

Static analysis reported external command and weak cryptography patterns, but review found those were false positives from Markdown code fences, inline code, metadata text, and checklist wording. The network patterns are expected educational examples for SSE, WebSocket, fetch, and documentation links. One low-severity template issue remains because an error message is interpolated directly into an SSE JSON event.

Pure documentation and code template skill. All static findings are false positives caused by markdown code formatting (backticks) misidentified as shell commands, and documentation references to cryptographic algorithms (in URLs/specifications) misidentified as weak crypto usage. The skill contains no executable scripts, network calls, or filesystem operations beyond its own files.

Pure documentation and code template skill. All static findings are false positives caused by markdown code formatting (backticks) misidentified as shell commands, and documentation references to cryptographic algorithms (in URLs/specifications) misidentified as weak crypto usage. The skill contains no executable scripts, network calls, or filesystem operations beyond its own files.

Pure documentation and code template skill containing no executable scripts, network calls, or filesystem access beyond its own files. All code examples are educational patterns for streaming API implementation.

Pure documentation and code template skill containing no executable scripts, network calls, or filesystem access beyond its own files. All code examples are educational patterns for streaming API implementation.

Pure documentation and code template skill containing no executable scripts, network calls, or filesystem access beyond its own files. All code examples are educational patterns for streaming API implementation.