ci: harden pipeline with bandit SAST and pinned jscpd

[NITISH-R-G]

This PR hardens the Continuous Integration pipeline and resolves tooling flakiness to initiate Cycle 8.

Improvements:

• Added Static Application Security Testing (SAST) via bandit.
• Integrated domain-specific validation via openenv validate directly into GitHub Actions.
• Fixed jscpd platform errors by pinning it to version 4.0.0 and extending the ignore list to skip build artifacts.
• Resolved dynamic typing false-positives with mypy in viz/gradio_demo.py.
• Included the Cycle 8 report tracking metrics improved.

---

PR created automatically by Jules for task 10940384906517376372 started by @NITISH-R-G

Summary by Sourcery

Harden the CI code-quality workflow with security and domain validation checks while stabilizing duplicate-code detection and resolving type-checking noise in the demo UI.

New Features:

• Add Bandit-based static application security testing to the Python code-quality GitHub Actions workflow.
• Integrate OpenEnv domain-specific validation into the CI pipeline.
• Introduce a Cycle 8 repository health and CI improvement report document.

Bug Fixes:

• Pin the jscpd version and extend its ignore patterns to avoid CI breakages from build artifacts and platform issues.
• Suppress spurious mypy attribute-defined errors on Gradio button click handlers in the demo UI.

Enhancements:

• Add Bandit as a development dependency and include it in the CI dependency installation list to support SAST in development and CI environments.

CI:

• Update the code-quality GitHub Actions workflow to install and run Bandit and OpenEnv validation as part of the CI checks.
• Pin jscpd to a specific version in the frontend-quality workflow to ensure stable duplicate-code analysis and ignore build output directories.

Documentation:

• Add a Cycle 8 report documenting repository health, CI weaknesses, planned improvements, and resulting metrics.

[google-labs-jules]

👋 Jules, reporting for duty! I'm here to lend a hand with this pull request.

When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down.

I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job!

For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with @jules. You can find this option in the Pull Request section of your global Jules UI settings. You can always switch back!

New to Jules? Learn more at jules.google/docs.

---

For security, I will only act on instructions from the user who triggered this task.

[greptile-apps]

Your trial has ended. Reactivate Greptile to resume code reviews.

[coderabbitai]

Important

Review skipped

Draft detected.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro Plus

Run ID: 1f139d2e-891a-4c7a-a8a1-8cee1f908a6d

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[sourcery-ai]

Reviewer's Guide

This PR hardens the CI code-quality workflow by adding Bandit SAST and OpenEnv validation, stabilizes the frontend duplicate-code check by pinning jscpd and broadening ignore patterns, quiets mypy on Gradio click handlers, and documents the Cycle 8 CI improvements in a new report markdown file.

Flow diagram for updated CI code-quality workflow

flowchart TD
  GitHubActions[[GitHub Actions code-quality workflow]]

  GitHubActions --> BackendQuality[Backend-quality job]
  GitHubActions --> FrontendQuality[Frontend-quality job]

  BackendQuality --> InstallPythonDeps[Install Python deps
  ruff, mypy, pydantic, vulture, radon, bandit, openenv-core]
  InstallPythonDeps --> RunRuff[Run Ruff]
  RunRuff --> RunMypy[Run mypy]
  RunMypy --> RunRadon[Run radon]
  RunRadon --> RunBandit[Run bandit SAST
  python -m bandit -r . -c pyproject.toml]
  RunBandit --> RunPytest[Run pytest]
  RunPytest --> RunOpenEnv[Run openenv validate .]

  FrontendQuality --> InstallNodeDeps[Setup Node and install jscpd@4.0.0]
  InstallNodeDeps --> RunJscpd[Run jscpd
  ignore json, md, yaml, node_modules, venv, .venv, dist, build]

Loading

File-Level Changes

Change	Details	Files
Strengthen backend CI code-quality workflow with security scanning and domain validation tooling.	Extend Python dependency installation in the code-quality workflow to include bandit and openenv-core. Add a dedicated GitHub Actions step to run Bandit against the repository using pyproject.toml configuration. Add a dedicated GitHub Actions step to run openenv validate over the repository.	.github/workflows/code-quality.yml
Stabilize frontend duplicate-code scanning in CI by pinning jscpd and ignoring build artifacts.	Pin the globally installed jscpd npm package to version 4.0.0 in the workflow. Extend jscpd ignore globs to skip dist and build directories in addition to existing exclusions.	.github/workflows/code-quality.yml
Resolve mypy false positives on Gradio click handlers in the demo visualization module.	Annotate Gradio click invocations with type: ignore[attr-defined] comments where mypy flags missing attributes on UI components.	viz/gradio_demo.py
Ensure Bandit is available as a development dependency for local tooling parity with CI.	Add bandit with a minimum version constraint to the dev extras section of pyproject.toml.	pyproject.toml
Add documentation for Cycle 8 repository health and CI hardening outcomes.	Create a new report markdown file describing CI weaknesses, improvements, sprint plan, and metrics for Cycle 8.	CYCLE_8_REPORT.md

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[github-actions]

Failed to generate code suggestions for PR

[greptile-apps]

Your trial has ended. Reactivate Greptile to resume code reviews.

[greptile-apps]

Your trial has ended. Reactivate Greptile to resume code reviews.

[greptile-apps]

Your trial has ended. Reactivate Greptile to resume code reviews.