You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+22-1Lines changed: 22 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -25,7 +25,8 @@ from your **GitHub Workflows**.
25
25
-[Check for compliance issues](#check-for-compliance-issues)
26
26
-[Define a custom project name](#define-a-custom-project-name)
27
27
-[Install ScanCode.io from a repository branch](#install-scancodeio-from-a-repository-branch)
28
-
-[Where does the scan results go?](#where-does-the-scan-results-go)
28
+
-[Run source to binary mapping](#run-source-to-binary-mapping)
29
+
-[Where does the scan results go?](#where-are-the-scan-results)
29
30
30
31
## Usage
31
32
@@ -226,6 +227,26 @@ Activate this behavior by enabling `check-compliance` and setting
226
227
scancodeio-repo-branch: "main"
227
228
```
228
229
230
+
### Run source to binary mapping
231
+
232
+
Use this [workflow template](.github/workflows/map-deploy-to-develop-template.yml) for validating the integrity of open-source binary. It compares a project’s binary to its source code. Workflow will generate mapping between compiled binary and its original source code, which helps in spotting any malicious, unexpected, or otherwise undesirable code that may have made its way into the final binary.
233
+
234
+
#### To use follow these steps:
235
+
236
+
1. In your workflow add job to build binary and upload it as a GitHub actions artifact.
237
+
2. Now add a second job to run source binary mapping using [template](.github/workflows/map-deploy-to-develop-template.yml).
0 commit comments