Historial de auditorías

Most static alerts are false positives caused by Markdown formatting, documentation links, and benign command substitutions. Confirmed risks include arithmetic evaluation, unsafe Actions interpolation, unpinned packages, and unauthenticated comment commands. Destructive repository automation also requires explicit approval.

Most backtick, template-literal, URL, filesystem, and reconnaissance alerts are Markdown or documentation false positives. The real risks are intended Bash workflows that run external GitHub and npx commands while processing untrusted issue and project data. No malicious prompt-injection instruction was found; the quoted phrase appears in defensive guidance.

Static findings are mostly Markdown code fences, inline code, placeholder URLs, and CLI examples; no prompt-injection text or hidden malicious instructions were found. The main risks are operational: unpinned npx tools and examples that can mutate GitHub issues or projects if run without review.

Static analysis reported many external command, network, filesystem, and weak crypto patterns, but most are Markdown examples for GitHub CLI, ruv-swarm, Claude Flow, project URLs, and templates. The high weak cryptography alerts are false positives; no prompt injection, credential theft, obfuscation, or unauthorized exfiltration was found. Risk remains medium because following the guide runs third-party CLIs and automation that can modify GitHub issues, projects, webhooks, and reports.

This is a documentation-only skill containing example bash scripts for GitHub CLI operations. The static analyzer flagged 185 potential issues, but 99% are false positives. The 'shell backtick execution' findings are actually POSIX shell command substitution ($()) used in legitimate gh CLI examples. The 'weak cryptographic algorithm' findings are misidentified base64 strings in URLs/metadata. The 'system reconnaissance' findings are standard GitHub CLI commands (gh issue list, gh project list) for project management. All detected patterns are standard documentation for a legitimate GitHub project management tool.

This is a documentation-only skill containing example bash scripts for GitHub CLI operations. The static analyzer flagged 185 potential issues, but 99% are false positives. The 'shell backtick execution' findings are actually POSIX shell command substitution ($()) used in legitimate gh CLI examples. The 'weak cryptographic algorithm' findings are misidentified base64 strings in URLs/metadata. The 'system reconnaissance' findings are standard GitHub CLI commands (gh issue list, gh project list) for project management. All detected patterns are standard documentation for a legitimate GitHub project management tool.

This skill provides legitimate GitHub project management capabilities using CLI tools and MCP servers. While it requires broad permissions for GitHub operations and executes external commands, these capabilities are necessary for its stated purpose. The skill uses standard GitHub CLI (gh) and documented MCP tools without any obfuscated or suspicious code patterns.

This skill provides legitimate GitHub project management capabilities using CLI tools and MCP servers. While it requires broad permissions for GitHub operations and executes external commands, these capabilities are necessary for its stated purpose. The skill uses standard GitHub CLI (gh) and documented MCP tools without any obfuscated or suspicious code patterns.