RFP.2.2 demo: severity gate — blocks on Critical & High#3
Open
dave-apisec wants to merge 11 commits into
Open
Conversation
Demonstrates RFP.2.1 + RFP.2.2 — PR-triggered scan, runner isolation, secret-based credential handling, and severity gating: - APISEC_MAX_HIGH: "0" → any High finding blocks the PR - Medium advisory runs with continue-on-error (warns, does not block)
Tightens RFP.2.2 demo to a single blocking step: APISEC_MAX_CRITICAL=0 and APISEC_MAX_HIGH=0. Container exits non-zero on any Critical or High finding, which fails the check and prevents merge.
…URL to PR comment
APIsec API Security Scan
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
PR-triggered APIsec scan with blocking gate on Critical & High severity findings (APISEC_MAX_CRITICAL=0, APISEC_MAX_HIGH=0).