lerer/Veracode Software Composition Analysis
An action to execute Veracode Agent-Based SCA and import findings as issues
View on GitHubTrust Signals
- Scorecard Score
- not yet scored
- Maintenance Recency
- Stale
- License
- None
- Runtime
- Deprecated runtime
Inputs
| name | description | required | default |
|---|---|---|---|
| github_token | Authorization token to query and create issues | yes | — |
| quick | — | no | false |
| update_advisor | Show update advisor | no | false |
| url | A git URL to work with in case the scan is not for the current repository | no | "" |
| min-cvss-for-issue | The minimum CVSS value for vulnerability to be added as an issue | no | 0 |
| fail-on-cvss | The maximum allowed cvss in found vulnerabilities to pass the step | no | 10 |
| create-issues | An attribute to instruct the action to create an issue from found vulnerability or just simple text output | no | false |
| path | A path within the repository where the build definition starts | no | . |
| debug | Run the SRCCLR in debug mode | no | false |
| skip-collectors | Run the SRCCLR with the `--skip-collectors` options | no | false |
| allow-dirty | Run the SRCCLR with the `--allow-dirty` option | no | false |
| recursive | Run the SRCCLR with the `--recursive` option | no | false |
Outputs
no outputs