datatheorem/Data Theorem Mobile Secure
Uploads your pre-production mobile app binaries to Data Theorem for scanning.
View on GitHubTrust Signals
- Scorecard Score
- not yet scored
- Maintenance Recency
- Stale
- License
- None
Inputs
| name | description | required | default |
|---|---|---|---|
| DT_UPLOAD_API_KEY | Data Theorem upload API key | yes | — |
| DT_RESULTS_API_KEY | Data Theorem results API key (required when BLOCK_ON_SEVERITY is used) | no | — |
| UPLOAD_BINARY_PATH | Path to the app to upload. You can use a glob pattern to indicate variable parts of the build's file name (for example, if the app's version number or build date is in the file name). Examples of glob patterns: - `app-*.apk` : search for any apk starting with `app-` in workspace root directory - `**/app-*.ipa` : search for any ipa starting with `app-` in any subdirectory of the workspace - `{,**/}app-debug*.*` : search for any file containing `app-debug` in root the directory or in any subdirectory of the workspace If multiple files match the provided pattern all matching files will be uploaded. The pattern should not match more than 3 files. | yes | — |
| SOURCEMAP_FILE_PATH | Path to the sourcemap file used to map obfuscated symbols to their original code name | no | — |
| USERNAME | Username to be used for authenticated testing of the application. If provided, will override the previosly provided value. | no | — |
| PASSWORD | Password to be used for authenticated testing of the application. If provided, will override the previosly provided value. Use of GitHub secrets is recommended. | no | — |
| COMMENTS | Miscellaneous, free-form comments regarding the upload. | no | — |
| RELEASE_ID | A custom ID associated with the binary being submitted, since the app version may not change very often. It is recommended that you use a unique value for this, such as the CI/CD job ID. If not set, Data Theorem will assign the binary a release_id. | no | — |
| PLATFORM_VARIANT | The variant of the platform to use for scanning; Currently, the accepted value is IOS_ON_MAC (scan an iOS build on an Apple Silicon Mac instead of on an iOS device, in order to exercise code paths that are specific to Macs.) | no | — |
| EXTERNAL_ID | The external_id field represents your organization’s custom identifier for the app, if any. | no | — |
| BLOCK_ON_SEVERITY | Block the build if vulnerabilities with the specified minimum severity are found. Valid values: HIGH, MEDIUM, LOW. If not specified, build will not be blocked. | no | — |
| WARN_ON_SEVERITY | Print warning messages if vulnerabilities with the specified minimum severity are found. This is a softer version of BLOCK_ON_SEVERITY that doesn't fail the build. Valid values: HIGH, MEDIUM, LOW. If not specified, no warnings will be shown. This requires a Data Theorem Mobile Results API Key to be set. | no | — |
| POLLING_TIMEOUT | Stop polling the scan result after the specified time in seconds, default is 5 minutes. | no | — |
| WAIT_FOR_STATIC_SCAN_ONLY | When enabled, waits for the static_scan to be COMPLETED instead of the top-level scan. Default is false. | no | — |
| SEVERITY_CHECK_SCOPE | Controls whether BLOCK_ON_SEVERITY and WARN_ON_SEVERITY check only findings from the current scan or all open findings in the mobile app. Valid values: CURRENT_SCAN, ALL_ISSUES - CURRENT_SCAN: Check only findings discovered in the current scan (default) - ALL_ISSUES: Check all open findings associated with the mobile app Default: CURRENT_SCAN | no | CURRENT_SCAN |
Outputs
no outputs