Historial de auditorías
payment-engineer - 4 auditorías
Comparación de versiones
Cambios de capacidades y hallazgos entre versiones auditadas, primero las más recientes.
| Versión | Fecha | Resultado | Elementos de revisión | Cambio vs anterior |
|---|---|---|---|---|
| v4 Más reciente | 23 jul 2026, 23:49 | Sin hallazgos confirmados | 0 | Sin cambios de capacidad |
| v3 | 15 jul 2026, 15:28 | Sin hallazgos confirmados | 0 | Sin cambios de capacidad |
| v2 | 15 jul 2026, 15:28 | Sin hallazgos confirmados | 0 | Sin cambios de capacidad |
| v1 | 15 jul 2026, 15:28 | Sin hallazgos confirmados | 0 | Base |
23 jul 2026, 23:49
All 20 static findings are false positives caused by Markdown fences, inline code formatting, or multilingual text. The skill is a documentation-only payment engineering guide with no executable commands, system reconnaissance, obfuscation, or prompt injection.
Factores de riesgo
⚙️ Comandos externos (18)
15 jul 2026, 15:28
All 18 external-command findings are false positives caused by Markdown fences or inline code formatting. The reconnaissance and entropy findings are also false positives; the readable documentation contains no command execution, obfuscation, or prompt injection.
Factores de riesgo
⚙️ Comandos externos (18)
15 jul 2026, 15:28
All 18 external-command findings are false positives caused by Markdown fences or inline code formatting. The reconnaissance and entropy findings are also false positives; the readable documentation contains no command execution, obfuscation, or prompt injection.
Factores de riesgo
⚙️ Comandos externos (18)
15 jul 2026, 15:28
All 18 external-command findings are false positives caused by Markdown fences or inline code formatting. The reconnaissance and entropy findings are also false positives; the readable documentation contains no command execution, obfuscation, or prompt injection.