Skip to content

feat(security): add CodeQL automated scanning workflow - #63652

Closed
AnzalKhan16 wants to merge 1 commit into
SAPTARSHI-coder:mainfrom
AnzalKhan16:feature/codeql-workflow
Closed

feat(security): add CodeQL automated scanning workflow#63652
AnzalKhan16 wants to merge 1 commit into
SAPTARSHI-coder:mainfrom
AnzalKhan16:feature/codeql-workflow

Conversation

@AnzalKhan16

Copy link
Copy Markdown
Contributor

Pull Request Description

This PR introduces a GitHub Actions workflow that performs automated CodeQL analysis to identify potential security vulnerabilities and code quality issues within the repository. It integrates static application security testing (SAST) into the CI pipeline.


Type of Change

  • ✨ New animation / hover effect
  • 🧩 New component
  • 📝 Documentation improvement
  • 🐛 Bug fix in an existing submission
  • Other (describe below)
    • Security scanning workflow (CodeQL)

Submission Checklist

⚠️ PRs that fail this checklist will be closed without review.

  • All changes are inside submissions/ (e.g., submissions/examples/your-feature-name/ or submissions/docs/your-feature-name/) (N/A - Security & CI update)
  • Includes demo.html — self-contained, opens in browser with no server (N/A)
  • Includes style.css — raw CSS for the proposed feature (N/A)
  • Includes README.md — what it does, how to use it, why it fits EaseMotion CSS (Updated SECURITY.md instead)
  • No changes to core/
  • No changes to components/
  • One feature per PR (no bundled unrelated changes)

Feature Description

What does this add?

It adds .github/workflows/codeql.yml to automatically run GitHub's CodeQL analysis on PRs, pushes to main, and via a weekly schedule, and documents this in SECURITY.md.

How does a developer use it?

# Runs automatically in CI
# No manual intervention required from developers

fixes #63649 

@github-advanced-security

Copy link
Copy Markdown

You are seeing this message because GitHub Code Scanning has recently been set up for this repository, or this pull request contains the workflow file for the Code Scanning tool.

What Enabling Code Scanning Means:

  • The 'Security' tab will display more code scanning analysis results (e.g., for the default branch).
  • Depending on your configuration and choice of analysis tool, future pull requests will be annotated with code scanning analysis results.
  • You will be able to see the analysis results for the pull request's branch on this overview once the scans have completed and the checks have passed.

For more information about GitHub Code Scanning, check out the documentation.

@SAPTARSHI-coder SAPTARSHI-coder added the invalid This doesn't seem right label Aug 6, 2026
@SAPTARSHI-coder

Copy link
Copy Markdown
Owner

❌ PR Closed — Files Outside submissions/ Folder

@AnzalKhan16, this PR has been automatically closed because it modifies files outside the allowed submissions/ directory:

  • .github/workflows/codeql.yml
  • SECURITY.md

What to do

Contributions must only add files inside the submissions/ folder. Please:

  1. Create a new branch
  2. Add only your submission files under submissions/examples/your-feature-name/
  3. Open a new PR

See the contribution guide for details.

— EaseMotion CSS Guard

@SAPTARSHI-coder

Copy link
Copy Markdown
Owner

❌ Submission Validation Failed

Thank you for your contribution! However, some required files are missing or incorrect.

📋 Required Structure

submissions/your-category/your-feature-name/ (e.g., submissions/examples/ or submissions/docs/)
├── demo.html     ← Interactive demo with DOCTYPE, html, head, body tags
├── style.css     ← Your original CSS (not copy-pasted from a template)
└── README.md     ← Brief description of your feature

🔍 Issues Found:

🔠 Strict Code Integrity Protection

  • ❌ Repository rule violation: You are not allowed to change existing code. Modified existing files: SECURITY.md.

🔠 Core Framework Protection

  • ❌ PR modifies core framework/configuration files: .github/workflows/codeql.yml, SECURITY.md. Contributors may only modify files inside the submissions/ directory.

🔠 Submission Folder Protection

  • ❌ This PR does not contain any additions inside the submissions/ directory. Contributors must place their submissions under the submissions/ directory (e.g. submissions/examples/your-feature-name/ or submissions/docs/your-feature-name/).

📝 How to Fix:

  1. Ensure all 3 files exist with real, original content
  2. demo.html must have <!DOCTYPE html>, <html>, <head>, <body> tags
  3. style.css must contain your own CSS (not copy-pasted boilerplate)
  4. Push fixes to this branch — the validator will re-run automatically

📖 See CONTRIBUTING.md for full guidelines.

@SAPTARSHI-coder

Copy link
Copy Markdown
Owner

🔒 Pull Request Closed

This PR was automatically closed because it failed the submission validation check.

Please fix the issues listed above, then open a new pull request. Thank you!

@SAPTARSHI-coder

Copy link
Copy Markdown
Owner

🔒 Pull Request Closed: This PR has been automatically closed because it does not contain any file changes under the submissions/ directory. Contributors must place their submissions under the submissions/ directory (e.g., submissions/examples/your-feature-name/ or submissions/docs/your-feature-name/). Thank you!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants