← Home

appium-remote-debugger

npm Repository Homepage

Appium proxy for Remote Debugger protocol

42
Versions
Apache-2.0
License
No
Install Scripts
Verified
Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures gitHead linked

Maintainers

jlippsnick.mokhnachkazucocoaimurchiedangraham

Keywords

appium

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
semgrep semgrep:env-spread AI (semgrep): Build script spreads env only to sanitize Android SDK vars before Bazel invocation; no exfiltration risk. ai

Versions (showing 42 of 42)

Version Deps Published
15.10.3 7 / 27
15.10.2 7 / 27
15.10.1 7 / 27
15.10.0 7 / 27
15.9.1 7 / 21
15.9.0 7 / 21
15.8.1 7 / 21
15.8.0 7 / 21
15.7.3 9 / 23
15.7.2 9 / 23
15.7.1 9 / 23
15.7.0 9 / 23
15.6.0 9 / 23
15.5.0 9 / 23
15.4.0 9 / 23
15.3.5 9 / 23
15.3.4 9 / 23
15.3.3 9 / 23
15.3.2 9 / 23
15.3.1 9 / 23
15.3.0 9 / 23
15.2.14 9 / 23
15.2.13 9 / 23
15.2.12 9 / 23
15.2.11 9 / 23
15.2.10 9 / 23
15.2.9 9 / 23
15.2.8 9 / 23
15.2.7 9 / 23
15.2.6 10 / 23
15.2.5 10 / 23
15.2.4 10 / 23
15.2.3 10 / 23
15.2.2 10 / 23
15.2.1 10 / 23
15.2.0 10 / 23
15.1.1 10 / 23
15.1.0 10 / 23
15.0.3 10 / 23
15.0.2 10 / 23
15.0.1 10 / 23
15.0.0 10 / 23

v15.10.3

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v15.10.2

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v15.10.1

2 findings
HIGH env-spread: scripts/common.mjs:88 semgrep

Spreading entire process.env into an object — may capture all secrets Source: https://github.com/appium/appium-remote-debugger/blob/407560aad94b84633eec11a98acea469802aca3e/scripts/common.mjs#L88 86 | // Selenium atoms build does not require Android SDK. If these env vars are set locally, 87 | // Bazel may try to auto-configure Android toolchains and fail on host-specific SDK issues. > 88 | const env = {...process.env}; 89 | delete env.ANDROID_HOME; 90 | delete env.ANDROID_SDK_ROOT;

INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v15.10.0

2 findings
HIGH env-spread: scripts/common.mjs:88 semgrep

Spreading entire process.env into an object — may capture all secrets Source: https://github.com/appium/appium-remote-debugger/blob/b3d9dab9d4697f1d884a3795c0b6f80201383d11/scripts/common.mjs#L88 86 | // Selenium atoms build does not require Android SDK. If these env vars are set locally, 87 | // Bazel may try to auto-configure Android toolchains and fail on host-specific SDK issues. > 88 | const env = {...process.env}; 89 | delete env.ANDROID_HOME; 90 | delete env.ANDROID_SDK_ROOT;

INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v15.9.1

2 findings
HIGH env-spread: scripts/common.mjs:88 semgrep

Spreading entire process.env into an object — may capture all secrets Source: https://github.com/appium/appium-remote-debugger/blob/6afc2ee1c90f05af43e225b48176078cc10064f9/scripts/common.mjs#L88 86 | // Selenium atoms build does not require Android SDK. If these env vars are set locally, 87 | // Bazel may try to auto-configure Android toolchains and fail on host-specific SDK issues. > 88 | const env = {...process.env}; 89 | delete env.ANDROID_HOME; 90 | delete env.ANDROID_SDK_ROOT;

INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v15.9.0

2 findings
HIGH env-spread: scripts/common.mjs:88 semgrep

Spreading entire process.env into an object — may capture all secrets Source: https://github.com/appium/appium-remote-debugger/blob/b1c25b7f1876192e8e5bc54c57faa82de38e06e0/scripts/common.mjs#L88 86 | // Selenium atoms build does not require Android SDK. If these env vars are set locally, 87 | // Bazel may try to auto-configure Android toolchains and fail on host-specific SDK issues. > 88 | const env = {...process.env}; 89 | delete env.ANDROID_HOME; 90 | delete env.ANDROID_SDK_ROOT;

INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v15.8.1

2 findings
HIGH env-spread: scripts/common.mjs:88 semgrep

Spreading entire process.env into an object — may capture all secrets Source: https://github.com/appium/appium-remote-debugger/blob/1fc9e70ac220cba44ffc1c3c439fbecaa695a700/scripts/common.mjs#L88 86 | // Selenium atoms build does not require Android SDK. If these env vars are set locally, 87 | // Bazel may try to auto-configure Android toolchains and fail on host-specific SDK issues. > 88 | const env = {...process.env}; 89 | delete env.ANDROID_HOME; 90 | delete env.ANDROID_SDK_ROOT;

INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v15.8.0

2 findings
HIGH env-spread: scripts/common.mjs:88 semgrep

Spreading entire process.env into an object — may capture all secrets Source: https://github.com/appium/appium-remote-debugger/blob/3cee63c546625b5771c9cf6aaa0f8a06c102a532/scripts/common.mjs#L88 86 | // Selenium atoms build does not require Android SDK. If these env vars are set locally, 87 | // Bazel may try to auto-configure Android toolchains and fail on host-specific SDK issues. > 88 | const env = {...process.env}; 89 | delete env.ANDROID_HOME; 90 | delete env.ANDROID_SDK_ROOT;

INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v15.7.3

2 findings
HIGH env-spread: scripts/common.mjs:46 semgrep

Spreading entire process.env into an object — may capture all secrets Source: https://github.com/appium/appium-remote-debugger/blob/948ae8d6593f47b647e16fb3bb9a7ef2634ddc03/scripts/common.mjs#L46 44 | // Selenium atoms build does not require Android SDK. If these env vars are set locally, 45 | // Bazel may try to auto-configure Android toolchains and fail on host-specific SDK issues. > 46 | const env = {...process.env}; 47 | delete env.ANDROID_HOME; 48 | delete env.ANDROID_SDK_ROOT;

INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v15.7.2

2 findings
HIGH env-spread: scripts/common.mjs:46 semgrep

Spreading entire process.env into an object — may capture all secrets Source: https://github.com/appium/appium-remote-debugger/blob/03f92f6a3ee63a26fb944d253bd08e236c725cb9/scripts/common.mjs#L46 44 | // Selenium atoms build does not require Android SDK. If these env vars are set locally, 45 | // Bazel may try to auto-configure Android toolchains and fail on host-specific SDK issues. > 46 | const env = {...process.env}; 47 | delete env.ANDROID_HOME; 48 | delete env.ANDROID_SDK_ROOT;

INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v15.7.1

2 findings
HIGH env-spread: scripts/common.mjs:46 semgrep

Spreading entire process.env into an object — may capture all secrets Source: https://github.com/appium/appium-remote-debugger/blob/3dd2480fdac26495d04877a1f0edcea7abfcc81d/scripts/common.mjs#L46 44 | // Selenium atoms build does not require Android SDK. If these env vars are set locally, 45 | // Bazel may try to auto-configure Android toolchains and fail on host-specific SDK issues. > 46 | const env = {...process.env}; 47 | delete env.ANDROID_HOME; 48 | delete env.ANDROID_SDK_ROOT;

INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v15.7.0

2 findings
HIGH env-spread: scripts/common.mjs:46 semgrep

Spreading entire process.env into an object — may capture all secrets Source: https://github.com/appium/appium-remote-debugger/blob/4e87dc5a7882f384ecb363b2be7a7087ee63a54d/scripts/common.mjs#L46 44 | // Selenium atoms build does not require Android SDK. If these env vars are set locally, 45 | // Bazel may try to auto-configure Android toolchains and fail on host-specific SDK issues. > 46 | const env = {...process.env}; 47 | delete env.ANDROID_HOME; 48 | delete env.ANDROID_SDK_ROOT;

INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v15.6.0

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v15.5.0

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v15.4.0

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v15.3.5

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v15.3.4

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v15.3.3

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v15.3.2

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v15.3.1

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v15.3.0

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v15.2.14

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v15.2.13

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v15.2.12

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v15.2.11

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v15.2.10

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v15.2.9

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v15.2.8

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v15.2.7

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v15.2.6

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v15.2.5

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v15.2.4

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v15.2.3

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v15.2.2

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v15.2.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v15.2.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v15.1.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v15.1.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v15.0.3

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v15.0.2

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v15.0.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v15.0.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.