divyansh42/CRDA
Analyse Vulnerabilities in application dependencies
View on GitHubTrust Signals
- Scorecard Score
- not yet scored
- Maintenance Recency
- Stale
- License
- None
- Runtime
- Deprecated runtime
Inputs
| name | description | required | default |
|---|---|---|---|
| manifest_file_path | Path of the manifest file to use for analysis | yes | — |
| analysis_report_file_name | Name of the file to save the analysis report. | no | crda_analysis_report |
| snyk_token | Snyk token to be used to authenticate to CRDA | no | — |
| crda_key | Existing CRDA key to identify the existing user | no | — |
| consent_telemetry | CRDA collects anonymous usage data, and is disabled by default. If you want this behaviour set this to true | no | false |
| fail_on_vulnerability | Fail the workflow if vulnerability is found in the project. This will lead to workflow failure and sarif file would not be obtained. To set failure when vulnerability severity level is either "error" or "warning" set this input to "error". By default it is set to fail when severity level is "warning", or if you don't want to fail the action set this input to "false" | no | error |
Outputs
| name | description |
|---|---|
| crda_key | Generated CRDA key for future use |
| crda_report_json | Generated CRDA Analysis Report in JSON format |
| crda_report_sarif | Generated CRDA Analysis Report in Sarif format |
| report_link | CRDA analysis report link |