Add optional dependencies example in README

Signed-off-by: Keshav Priyadarshi <git@keshav.space>

Author: keshav-space

README.md

@@ -25,6 +25,7 @@ from your **GitHub Workflows**.
   - [Check for compliance issues](#check-for-compliance-issues)
   - [Define a custom project name](#define-a-custom-project-name)
   - [Install ScanCode.io from a repository branch](#install-scancodeio-from-a-repository-branch)
+  - [Install ScanCode.io with optional dependencies](#install-scancodeio-with-optional-dependencies)
   - [Run source to binary mapping](#run-source-to-binary-mapping)
 - [Where does the scan results go?](#where-are-the-scan-results)
 
@@ -227,6 +228,14 @@ Activate this behavior by enabling `check-compliance` and setting
     scancodeio-repo-branch: "main"
 ```
 
+### Install ScanCode.io with optional dependencies
+
+```yaml
+- uses: aboutcode-org/scancode-action@beta
+  with:
+    scancodeio-extras: "android_analysis,mining"
+```
+
 ### Run source to binary mapping
 
 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.