Improve SAST monorepo SARIF coverage gates#1541
Open
bozicovichsantiago20-oss wants to merge 1 commit into
Open
Improve SAST monorepo SARIF coverage gates#1541bozicovichsantiago20-oss wants to merge 1 commit into
bozicovichsantiago20-oss wants to merge 1 commit into
Conversation
4 tasks
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
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.
Skill Improvement ($50-150 Bounty)
Skill Modified
Skill name:
sast-configSkill path:
skills/devsecops/sast-config/What Was Wrong
Issue #1527 shows that the skill could report healthy repo-level CWE/ASVS SAST coverage while a polyglot monorepo only scans one package, one language, or one subdirectory. It also did not require SARIF/log evidence for included and excluded paths, generated/vendor LOC inflation, or per-release-component coverage.
What This PR Fixes
Not Evaluableguidance when scan artifacts cannot be tied back to production components.Evidence
Before: A single green CodeQL/Semgrep/Sonar job could be treated as repository-wide SAST maturity even if only the root package, one matrix language, or one
--subdirwas scanned.After: The skill requires a component-to-artifact matrix and path/SARIF evidence before marking coverage complete. Missing Go/Python services, generated/vendor LOC inflation, or stale/base-branch scan SHAs are explicitly classified as gaps.
Test Cases Added/Updated
tests/vulnerable/)tests/benign/)Validation performed:
git diff --checkNot Evaluable,automationDetails.id,--subdir, and CodeQL language matrixBounty Tier
Bounty Info
Related issue: #1527
Attempt: #1527 (comment)