🔍 Static Analysis Report - 2025-11-09 #3527
Closed
Replies: 2 comments 1 reply
-
|
/plan |
Beta Was this translation helpful? Give feedback.
1 reply
-
|
This discussion was automatically closed because it was created by an agentic workflow more than 1 week ago. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
🔍 Static Analysis Report - 2025-11-09
Executive Summary
Completed static analysis scan of 74 agentic workflows using actionlint (with shellcheck integration). The scan identified 953 linting findings across 73 workflows. The vast majority of findings (945 out of 953, or 99.2%) are false positives from shellcheck misinterpreting markdown backticks in heredoc documentation as command substitution.
Key Findings:
Tool Availability:
Analysis Summary
Findings by Tool
*Medium severity issues are SC2287 errors, which are false positives
Findings by Severity
Clustered Findings by Issue Type
Top 5 Issue Types
Issue Type Details
1. SC2006: Legacy Backticks (694 findings)
Description: "Use $(...) notation instead of legacy backticks"
Root Cause: Shellcheck is flagging backticks used in markdown code formatting within heredocs. The compiled workflows write prompt instructions to files using heredocs that contain markdown documentation with inline code blocks (e.g.,
/tmp/gh-aw/agent/).Example:
Assessment: ✅ FALSE POSITIVE - These are not command substitutions, just markdown formatting in documentation strings.
Affected Workflows: All 73 workflows with prompts
2. SC2287: Command Name Ending with '/' (251 findings)
Description: "This is interpreted as a command name ending with '/'. Double check syntax"
Root Cause: Related to SC2006 - shellcheck interprets the path after backticks as a command name with trailing slash.
Assessment: ✅ FALSE POSITIVE - Same root cause as SC2006, no actual syntax error.
Affected Workflows: All 73 workflows with prompts
3. SC2002: Useless Cat (3 findings)
Description: "Useless cat. Consider 'cmd < file | ..' or 'cmd file | ..' instead"
Assessment: 📝 Minor code style issue - Can be optimized but not a security concern.
Affected Workflows:
4. SC2086: Missing Quotes (3 findings)
Description: "Double quote to prevent globbing and word splitting"
Assessment: 📝 Minor issue - Should be reviewed to ensure variables are properly quoted.
Affected Workflows:
5. SC2215: Flag as Command Name (2 findings)
Description: "This flag is used as a command name. Bad line break or missing [ .. ]?"
Assessment: 📝 Minor issue - May indicate a formatting problem that should be reviewed.
Affected Workflows:
Top 10 Workflows by Issue Count
Fix Recommendations
Priority 1: Address False Positives (SC2006/SC2287)
Recommended Solution: Add shellcheck disable directives to heredoc blocks with markdown content.
Fix Template:
Rationale:
Impact: Would reduce findings from 953 to 8 (99.2% reduction)
Priority 2: Fix Minor Code Style Issues
SC2002 - Useless Cat (3 instances)
Review and potentially optimize
cat file | commandtocommand < filein:SC2086 - Missing Quotes (3 instances)
Review variable usage in super-linter workflow to ensure proper quoting.
SC2215 - Flag as Command (2 instances)
Review command syntax in blog-auditor and unbloat-docs workflows.
Historical Context
This is the first automated static analysis scan of the gh-aw repository workflows. No previous scan data available for comparison.
Baseline Established:
Recommendations
Immediate Actions
Short-term Actions
Long-term Actions
Implementation Guide
A detailed fix template has been created and stored in cache memory at:
/tmp/gh-aw/cache-memory/fix-templates/actionlint-sc2006-sc2287-heredoc-backticks.mdThis template provides:
Conclusion
The static analysis scan successfully identified no actual security vulnerabilities in the agentic workflows. The 953 findings are overwhelmingly false positives (99.2%) from shellcheck's conservative analysis of markdown formatting in heredoc documentation.
Security Posture: ✅ GOOD - No security issues detected
Code Quality: ✅ GOOD - Only 8 minor style issues across 74 workflows
Action Required: 📝 OPTIONAL - Consider addressing false positives for cleaner linting output
Full Detailed Findings by Workflow
Complete Workflow Analysis
Workflows with Most Issues
Below are detailed breakdowns for workflows with the highest number of findings:
1. unbloat-docs (23 issues)
2. super-linter (21 issues)
3. poem-bot (20 issues)
All Affected Workflows
Complete list of 73 workflows affected (1 workflow has no issues):
archie, artifacts-summary, audit-workflows, blog-auditor, brave, changeset, ci-doctor, cli-version-checker, commit-changes-analyzer, copilot-agent-analysis, copilot-pr-nlp-analysis, copilot-pr-prompt-analysis, copilot-session-insights, craft, daily-doc-updater, daily-firewall-report, daily-news, daily-perf-improver, daily-repo-chronicle, daily-test-improver, dependabot-go-checker, dev-hawk, dev, developer-docs-consolidator, dictation-prompt, duplicate-code-detector, example-permissions-warning, example-workflow-analyzer, firewall, github-mcp-tools-report, go-logger, go-pattern-detector, grumpy-reviewer, instructions-janitor, issue-classifier, lockfile-stats, mcp-inspector, mergefest, notion-issue-summary, pdf-summary, plan, poem-bot, pr-nitpick-reviewer, prompt-clustering-analysis, python-data-charts, q, repo-tree-map, research, safe-output-health, schema-consistency-checker, scout, security-fix-pr, semantic-function-refactor, smoke-claude, smoke-codex, smoke-copilot, smoke-detector, static-analysis-report, super-linter, technical-doc-writer, test-claude-oauth-workflow, test-jqschema, test-manual-approval, test-ollama-threat-detection, test-post-steps, test-secret-masking, test-svelte, tidy, typist, unbloat-docs, video-analyzer, weekly-issue-summary
Workflow with No Issues
The following workflow has no actionlint findings:
Scan Metadata:
/tmp/gh-aw/cache-memory/security-scans/2025-11-09.jsonBeta Was this translation helpful? Give feedback.
All reactions