mre-fog/Data Theorem Mobile Secure

Uploads your pre-production mobile app binaries to Data Theorem for scanning.

View on GitHub

Trust Signals

Scorecard Score
not yet scored
Maintenance Recency
Stale
License
None
Runtime
Deprecated runtime
namedescriptionrequireddefault
DT_UPLOAD_API_KEYData Theorem upload API keyyes
UPLOAD_BINARY_PATHPath 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
USERNAMEUsername to be used for authenticated testing of the application. If provided, will override the previosly provided value. no
PASSWORDPassword to be used for authenticated testing of the application. If provided, will override the previosly provided value. Use of GitHub secrets is recommended. no
COMMENTSMiscellaneous, free-form comments regarding the upload. no
RELEASE_IDA 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_VARIANTThe 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_IDThe external_id field represents your organization’s custom identifier for the app, if any. no

no outputs