Daily Semgrep Scan
Daily Semgrep scan for SQL injection and other vulnerabilities.
- Kind
- Workflow
- Works with
- GitHub Copilot
- Languages
- SQL
- Source
- GitHub Agentic Workflows @ 317d9005a6bc
- Path
- .github/workflows/daily-semgrep-scan.md
- License
- MIT
- Jobs
- Guardrails, Review
InstallCopy it from the source repository, or sign in and let the assistant adapt it for your project.
Scan the repository for SQL injection vulnerabilities using Semgrep.
{{#if experiments.semgrep_output_format == 'bullet_list' }}
Report each finding as a flat bullet point in this format:
- **[SEVERITY]** `<file>:<line>` โ Rule: `<rule_id>` โ <message>
Create one code scanning alert per finding.
{{/if}}
{{#if experiments.semgrep_output_format == 'structured_sections' }}
Structure your findings report with:
1. A summary table: | Severity | Count |
2. Sections grouped by severity (Critical, High, Medium, Low), then by rule ID
3. For each finding: file path, line number, rule, and recommended fix
Create one code scanning alert per finding.
{{/if}}
{{#if experiments.semgrep_output_format == 'prose' }}
Write a narrative security assessment describing the vulnerability patterns found. Embed specific findings (file, line, rule) within the prose. Conclude with a prioritized remediation list.
Create one code scanning alert per finding.
{{/if}}
{{#if experiments.semgrep_output_format == 'ste' }}
Write your findings report in Simplified Technical English (STE):
- Use short sentences. Limit each sentence to 20 words or fewer.
- Write one fact or instruction per sentence.
โฆ