Historial de auditorías
finishing-a-development-branch - 5 auditorías
Versión de auditoría 5
Más reciente SeguroJan 16, 2026, 09:38 PM
This is a legitimate Git branch completion workflow skill. All 74 static findings are false positives: the analyzer incorrectly flagged 'git' commands as cryptographic operations, standard shell command capture for git output as injection risks, and routine output redirections as filesystem access. The skill performs standard git operations (checkout, merge, branch deletion, worktree cleanup) with proper safeguards including test verification, merge conflict detection, and user confirmations before destructive actions.
Factores de riesgo
🌐 Acceso a red (2)
⚙️ Comandos externos (61)
📁 Acceso al sistema de archivos (3)
Versión de auditoría 4
SeguroJan 16, 2026, 09:38 PM
This is a legitimate Git branch completion workflow skill. All 74 static findings are false positives: the analyzer incorrectly flagged 'git' commands as cryptographic operations, standard shell command capture for git output as injection risks, and routine output redirections as filesystem access. The skill performs standard git operations (checkout, merge, branch deletion, worktree cleanup) with proper safeguards including test verification, merge conflict detection, and user confirmations before destructive actions.
Factores de riesgo
🌐 Acceso a red (2)
⚙️ Comandos externos (61)
📁 Acceso al sistema de archivos (3)
Versión de auditoría 3
SeguroJan 10, 2026, 12:34 PM
Pure prompt-based skill containing only markdown documentation for git branch completion workflow. No executable code, no network calls, no file access beyond local git repository operations guided by user intent.
Versión de auditoría 2
SeguroJan 10, 2026, 12:34 PM
Pure prompt-based skill containing only markdown documentation for git branch completion workflow. No executable code, no network calls, no file access beyond local git repository operations guided by user intent.
Versión de auditoría 1
SeguroJan 10, 2026, 12:34 PM
Pure prompt-based skill containing only markdown documentation for git branch completion workflow. No executable code, no network calls, no file access beyond local git repository operations guided by user intent.