Skip to content

Commit fd8c966

Browse files
authored
Merge pull request #1 from danielcuthbert/main
added screenshots to readme
2 parents 6451ab8 + a619697 commit fd8c966

File tree

5 files changed

+33
-2
lines changed

5 files changed

+33
-2
lines changed

img/actionrunning.png

232 KB
Loading

img/mainyml.png

77.2 KB
Loading

img/output.png

404 KB
Loading

img/report.png

15.4 KB
Loading

readme.md

Lines changed: 33 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,9 +1,15 @@
11

2-
# Dependency check action
2+
# Welcome to Dependency check action
33

44
This action uses the docker image built every night in https://github.com/dependency-check/DependencyCheck_Builder. This image includes the updated vulnerabilities database so there is no need to update it. Therefore, it speeds up the test.
55

6-
By now, the action receives three parameters. Project name, scanpath and report format, but more parameters can be added as optional
6+
# What is Dependency-Check?
7+
8+
This action is based upon the OWASP Dependency-Check [tool](https://owasp.org/www-project-dependency-check/), a Software Composition Analysis (SCA) tool that attempts to detect publicly disclosed vulnerabilities contained within a project’s dependencies. It does this by determining if there is a Common Platform Enumeration (CPE) identifier for a given dependency. If found, it will generate a report linking to the associated CVE entries.
9+
10+
# How does it work?
11+
12+
The action receives three parameters: Project name, scanpath and report format, but more parameters can be added as optional.
713

814
Example:
915
```
@@ -32,3 +38,28 @@ jobs:
3238
name: Depcheck report
3339
path: ${{github.workspace}}/reports
3440
```
41+
42+
# How Do I Use It?
43+
We recommend adding the above example into your .github/workflows directory, using a name of your choice, in this example main.yml.
44+
45+
It should look like this
46+
47+
![](img/mainyml.png)
48+
49+
Once that action kicks off, you should be able to see it running in the actions tab.
50+
51+
![](img/actionrunning.png)
52+
53+
Finally, once it has completed, a report will be generated and accessible from the actions tab
54+
55+
![](img/report.png)
56+
57+
Downloading this and opening it in a browser will give you the following (for example)
58+
59+
![](img/output.png)
60+
61+
# Who Is Behind It?
62+
63+
Dependency check action was developed by the Santander UK Security Engineering team, namely:
64+
65+
- [Javier Domínguez Ruiz](https://github.com/javixeneize)

0 commit comments

Comments
 (0)