contentstack/Snyk SCA Scan Analysis
Composite action that reads snyk.json from the current directory, analyzes severities and SLA breaches, and posts a PR comment
View on GitHubTrust Signals
- Scorecard Score
- not yet scored
- Maintenance Recency
- Activelast commit Jun 30, 2026
- License
- MIT
Pinned Snippet
uses: contentstack/sca-policy@ee7db1a126b72f2dd5edfef2989728a08567b14c # no releases — HEAD as of 2026-07-11tags can be moved; commit SHAs can't. why a SHA?
Inputs
| name | description | required | default |
|---|---|---|---|
| MAX_CRITICAL_ISSUES | Maximum allowed critical issues (with fixes) | no | 10 |
| MAX_HIGH_ISSUES | Maximum allowed high issues (with fixes) | no | 25 |
| MAX_MEDIUM_ISSUES | Maximum allowed medium issues (with fixes) | no | 500 |
| MAX_LOW_ISSUES | Maximum allowed low issues (with fixes) | no | 1000 |
| SLA_CRITICAL_WITH_FIX | SLA days for critical vulnerabilities with fixes | no | 15 |
| SLA_HIGH_WITH_FIX | SLA days for high vulnerabilities with fixes | no | 30 |
| SLA_MEDIUM_WITH_FIX | SLA days for medium vulnerabilities with fixes | no | 90 |
| SLA_LOW_WITH_FIX | SLA days for low vulnerabilities with fixes | no | 180 |
| SLA_CRITICAL_NO_FIX | SLA days for critical vulnerabilities without fixes | no | 30 |
| SLA_HIGH_NO_FIX | SLA days for high vulnerabilities without fixes | no | 120 |
| SLA_MEDIUM_NO_FIX | SLA days for medium vulnerabilities without fixes | no | 365 |
| SLA_LOW_NO_FIX | SLA days for low vulnerabilities without fixes | no | 365 |
Outputs
| name | description |
|---|---|
| fail_build | true if any thresholds or SLAs were breached for issues with available fixes |
| warn_build | true if SLA breaches detected for issues without available fixes |