-
Notifications
You must be signed in to change notification settings - Fork 4.4k
ci: security report workflow disclaimer #36432
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
Co-authored-by: Copilot Autofix powered by AI <62310815+github-advanced-security[bot]@users.noreply.github.com>
| ); | ||
| if (botComment) { | ||
| const disclaimer = '\n\n---\n\n⚠️ **Experimental Feature**: This security report is currently in experimental phase. Results may include false positives and the rules are being actively refined. Please review findings carefully.'; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Are we not providing information about merge from main to avoid findings unrelated to the PR?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks, I missed adding that.
Will include it in the disclaimer as well
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Updated the disclaimer
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
|
Thank you for contributing! Your pull request will be updated from main and then merged automatically (do not update manually, and be sure to allow changes to be pushed to your fork). |
Merge Queue Status✅ The pull request has been merged at 1646c84 This pull request spent 8 seconds in the queue, with no time running CI. Required conditions to merge
|
|
Comments on closed issues and PRs are hard for our team to see. |

Fix SQS inline policy guard rule and add experimental disclaimer to security reports
Issue
sqs-no-world-accessible-inline.guardwas checking incorrect resource type and property pathSolution
Fixed SQS inline policy rule:
AWS::SQS::Queueresources toAWS::SQS::QueueInlinePolicyresources per CloudFormation documentationProperties.QueuePolicy.StatementtoProperties.PolicyDocument.StatementAdded experimental disclaimer:
Checklist
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license