Historique des audits
routeros-qemu-chr - 3 audits
Version de l’audit 3
Dernier Risque moyenMay 9, 2026, 03:51 PM
Static analysis detected 347 potential security patterns across 5 files. After semantic evaluation, all findings are FALSE POSITIVES. The skill uses external commands for QEMU invocation, which is the core purpose of this documentation. Network access is limited to mikrotik.com download URLs. No malicious intent or actual security vulnerabilities confirmed.
Problèmes à risque moyen (2)
Problèmes à risque faible (4)
Facteurs de risque
⚙️ Commandes externes (3)
🌐 Accès réseau (2)
📁 Accès au système de fichiers (2)
Version de l’audit 2
Risque faibleApr 16, 2026, 09:11 PM
Documentation and reference skill for running RouterOS CHR in QEMU. Static analysis flagged 343 patterns, but evaluation reveals these are false positives: shell backtick notation in markdown code examples (not execution), sudo in GitHub Actions CI (expected), MD5 references in kernel history docs (not actual usage), and legitimate acceleration detection commands. All network access targets MikroTik infrastructure for downloading CHR images. Risk level set to LOW due to external command patterns in documentation examples, but no actual malicious code present.
Problèmes à risque élevé (4)
Problèmes à risque moyen (3)
Problèmes à risque faible (2)
Facteurs de risque
⚙️ Commandes externes (3)
🌐 Accès réseau (2)
📁 Accès au système de fichiers (2)
Version de l’audit 1
SûrMar 30, 2026, 02:11 AM
Static analysis detected 303 potential security issues in code examples and documentation. All findings are false positives: external commands are legitimate QEMU invocations for virtualization, network operations access official MikroTik servers, and filesystem operations are standard QEMU configuration patterns. No malicious intent detected.