Skip to content

Conversation

@lperry022
Copy link
Contributor

I’ve updated the workflow trigger to pull_request_target so that the GitHub Actions bot has the correct permissions to post scanner results back to the PR.

With pull_request, the workflow runs in the context of the contributor’s fork, which restricts the default GITHUB_TOKEN to read-only. That’s why our OWASP scanner step was failing with a 403 error when trying to create comments.

Using pull_request_target makes the workflow execute in the base repo context, giving it issues: write and pull-requests: write permissions so it can safely create or update comments on the PR.

@lperry022 lperry022 requested review from a team as code owners September 24, 2025 05:03
@github-actions
Copy link

🔒 Security Scan Results

🔒 Security Scan Results
=========================

Bandit Scan Results:
-------------------
Run started:2025-09-24 05:03:33.649949

Test results:
	No issues identified.

Code scanned:
	Total lines of code: 1980
	Total lines skipped (#nosec): 0
	Total potential issues skipped due to specifically being disabled (e.g., #nosec BXXX): 1

Run metrics:
	Total issues (by severity):
		Undefined: 0
		Low: 13
		Medium: 0
		High: 0
	Total issues (by confidence):
		Undefined: 0
		Low: 0
		Medium: 0
		High: 13
Files skipped (1):
	./T1_2025/infra/backups/bak/controller/backend/v1.0.0/endpoints/register.py (syntax error while parsing AST from file)

No critical security issues detected.

The code has passed all critical security checks.

Copy link
Member

@ben-AI-cybersec ben-AI-cybersec left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👌

@ben-AI-cybersec ben-AI-cybersec merged commit 04fa1f0 into main Sep 24, 2025
1 check passed
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.

3 participants