Gathering detailed insights and metrics for appium-xcode
Gathering detailed insights and metrics for appium-xcode
Xcode related utilities. Get version number and path to executable.
Installations
npm install appium-xcodeDeveloper
appium
Developer Guide
BETA
Module System
CommonJS
Min. Node Version
>=14
Typescript Support
Yes
Node Version
20.16.0
NPM Version
10.8.2
Statistics
16 Stars
270 Commits
14 Forks
15 Watching
2 Branches
25 Contributors
Updated on 16 Oct 2024
Languages
JavaScript (100%)
Total Downloads
Cumulative downloads
Total Downloads
35,322,447
Last day
-10%
46,967
Compared to previous day
Last week
3.4%
253,916
Compared to previous week
Last month
20.3%
1,067,860
Compared to previous month
Last year
23%
9,101,339
Compared to previous year
Daily Downloads
Weekly Downloads
Monthly Downloads
Yearly Downloads
Dependencies
10
Dev Dependencies
18
Versions
appium-xcode
ES7 module for interacting with Xcode and Xcode-related functions. Used by various Appium drivers.
API
All functions are async, meaning they return promises which can be awaited via await.
Most functions are memoized, so after they are called once, they will simply return the same value. Remember that calling require() multiple times returns the same instantiation of a module if it has already been instantiated, so the memoization will be preserved across multiple files in the same project.
Some functions have an auto-retry built into them, they will retry silently a number of times. This is because the Xcode commands sometimes just flake and return bad values (or don't return).
getPath([timeout=15000])
memoized
gets path to Xcode Developer root.
getVersion([parse=false], [retries], [timeout])
memoized, retry
returns the version of Xcode formatted as a string, for example 6.3.1, or a version object if parse is true
getMaxIOSSDK([num_retries])
memoized, retry
returns the highest IOS SDK version supported by Xcode.
eg: '8.3'
getMaxTVOSSDK([num_retries])
memoized, retry
returns highest tvOS SDK version supported by Xcode.
eg: '10.1'
Develop
Test
npm test
npm e2e-test
Debug
After cloning appium-xcode, execute npm link in the appium-xcode directory. Next run npm link appium-xcode from the appium directory. This will symlink appium-xcode to node_modules/appium-xcode. If the clone becomes out of date remember to unlink or delete node_modules and reinstall.
For quick debugging you could cd into the node_modules/appium-xcode folder and run npm install followed by npm run build.
No vulnerabilities found.
Reason
no dangerous workflow patterns detected
Reason
no binaries found in the repo
Reason
0 existing vulnerabilities detected
Reason
license file detected
Details
- Info: project has a license file: LICENSE:0
- Info: FSF or OSI recognized license: Apache License 2.0: LICENSE:0
Reason
packaging workflow detected
Details
- Info: Project packages its releases by way of GitHub Actions.: .github/workflows/publish.js.yml:9
Reason
security policy file detected
Details
- Info: security policy file detected: github.com/appium/.github/SECURITY.md:1
- Info: Found linked content: github.com/appium/.github/SECURITY.md:1
- Warn: One or no descriptive hints of disclosure, vulnerability, and/or timelines in security policy
- Info: Found text in security policy: github.com/appium/.github/SECURITY.md:1
Reason
1 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
Reason
Found 2/22 approved changesets -- score normalized to 0
Reason
dependency not pinned by hash detected -- score normalized to 0
Details
- Info: Possibly incomplete results: error parsing job operating system: .github/workflows/functional-test.yml:34
- Info: Possibly incomplete results: error parsing job operating system: .github/workflows/functional-test.yml:36
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/functional-test.yml:26: update your workflow using https://app.stepsecurity.io/secureworkflow/appium/appium-xcode/functional-test.yml/master?enable=pin
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/functional-test.yml:27: update your workflow using https://app.stepsecurity.io/secureworkflow/appium/appium-xcode/functional-test.yml/master?enable=pin
- Warn: third-party GitHubAction not pinned by hash: .github/workflows/functional-test.yml:31: update your workflow using https://app.stepsecurity.io/secureworkflow/appium/appium-xcode/functional-test.yml/master?enable=pin
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/publish.js.yml:12: update your workflow using https://app.stepsecurity.io/secureworkflow/appium/appium-xcode/publish.js.yml/master?enable=pin
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/publish.js.yml:13: update your workflow using https://app.stepsecurity.io/secureworkflow/appium/appium-xcode/publish.js.yml/master?enable=pin
- Warn: third-party GitHubAction not pinned by hash: .github/workflows/unit-test.yml:14: update your workflow using https://app.stepsecurity.io/secureworkflow/appium/appium-xcode/unit-test.yml/master?enable=pin
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/unit-test.yml:24: update your workflow using https://app.stepsecurity.io/secureworkflow/appium/appium-xcode/unit-test.yml/master?enable=pin
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/unit-test.yml:25: update your workflow using https://app.stepsecurity.io/secureworkflow/appium/appium-xcode/unit-test.yml/master?enable=pin
- Warn: npmCommand not pinned by hash: .github/workflows/publish.js.yml:18
- Warn: npmCommand not pinned by hash: .github/workflows/unit-test.yml:29
- Info: 0 out of 6 GitHub-owned GitHubAction dependencies pinned
- Info: 0 out of 2 third-party GitHubAction dependencies pinned
- Info: 0 out of 2 npmCommand dependencies pinned
Reason
detected GitHub workflow tokens with excessive permissions
Details
- Warn: no topLevel permission defined: .github/workflows/functional-test.yml:1
- Warn: no topLevel permission defined: .github/workflows/publish.js.yml:1
- Warn: no topLevel permission defined: .github/workflows/unit-test.yml:1
- Info: no jobLevel write permissions found
Reason
no effort to earn an OpenSSF best practices badge detected
Reason
project is not fuzzed
Details
- Warn: no fuzzer integrations found
Reason
SAST tool is not run on all commits -- score normalized to 0
Details
- Warn: 0 commits out of 12 are checked with a SAST tool
Score
4.8
/10
Last Scanned on 2024-11-25
The Open Source Security Foundation is a cross-industry collaboration to improve the security of open source software (OSS). The Scorecard provides security health metrics for open source projects.
Learn More