Skip to content

Add dedicated SAST security audit CI - #1

Open
ARISAWSS wants to merge 3 commits into
masterfrom
ci-security
Open

ARISAWSS wants to merge 3 commits into
masterfrom
ci-security

Conversation

@ARISAWSS

@ARISAWSS ARISAWSS commented Aug 2, 2026

Copy link
Copy Markdown
Collaborator

Summary

  • Add a dedicated security_audit/ tooling folder with Bandit/Semgrep JSON helpers (normalize / report / diff), unit tests, and requirements.txt.
  • Introduce a new GitHub Actions workflow Security Audit (separate from the existing install CI) that scans TVWeb/app, TVSecure, and TVConnections, generates readable reports, and uploads artifacts.
  • Prepare a baseline folder so future runs can fail on new findings once reference JSON files are committed.

Test plan

  • Push to ci-security triggers workflow run
  • Run #2 (Harden empty SAST output handling.) completed successfully
  • Review artifacts on the successful Actions run (Bandit/Semgrep reports)
  • Confirm scanned paths are acceptable (TVWeb/app, TVSecure, TVConnections)
  • Decide later whether to commit a first baseline under security_audit/baseline/

Made with Cursor

arissaw20-source and others added 3 commits July 28, 2026 09:42
Separate SAST tooling from the install CI by adding Bandit and Semgrep helpers, a baseline-ready workflow, and artifact reports for iterative security review.

Co-authored-by: Cursor <cursoragent@cursor.com>
Keep the security audit tooling branch clean by removing test-generated cache files and preventing them from being recommitted.

Co-authored-by: Cursor <cursoragent@cursor.com>
Keep report generation stable by writing empty JSON payloads when Bandit or Semgrep do not emit an output file.

Co-authored-by: Cursor <cursoragent@cursor.com>

This branch has not been deployed

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants