File tree Expand file tree Collapse file tree 1 file changed +3
-2
lines changed Expand file tree Collapse file tree 1 file changed +3
-2
lines changed Original file line number Diff line number Diff line change @@ -11,7 +11,7 @@ A standalone tool that converts gosec results to Codacy's format. It allows the
11
11
12
12
2 . Converts gosec result into Codacy's format
13
13
14
- 3 . Prints Codacy's format to stdout
14
+ 3 . Prints Codacy's format to stdout
15
15
16
16
> NOTE: the tool must be run in the project root folder.
17
17
@@ -24,14 +24,15 @@ To get your gosec results into Codacy you'll need to:
24
24
- Enable the setting “Run analysis through build server” under your repository Settings > General > Repository analysis
25
25
- Obtain a [ project API token] ( https://docs.codacy.com/codacy-api/api-tokens/#project-api-tokens )
26
26
- Install [ gosec] ( https://github.com/securego/gosec#install )
27
+ - Download the ` codacy-gosec ` binary (or Java jar) from [ the releases page] ( https://github.com/codacy/codacy-gosec/releases )
27
28
28
29
29
30
### Sending the results to Codacy
30
31
31
32
Sending the results of running gosec to Codacy involves the steps below, which you can automate in your CI build process:
32
33
33
34
1 . Run gosec
34
- 2 . Convert the gosec output to a format that the Codacy API accepts
35
+ 2 . Convert the gosec output to a format that the Codacy API accepts using the [ codacy-gosec ] ( https://github.com/codacy/codacy-gosec/releases ) binary
35
36
3 . Send the results to Codacy
36
37
4 . Finally, signal that Codacy can use the sent results and start a new analysis
37
38
You can’t perform that action at this time.
0 commit comments