Node.js wrapper around chromedriver.
88%
Total Score
healthy
Frequent releases and active Appium backing outweigh concentrated commits and unpinned GitHub Actions.
A prepare script runs during installation or package preparation. This is a modest supply-chain surface, but the available artifact and repository evidence provide no indication that it is unsafe.
Five accounts have publish access, with two using the Sauce Labs domain and three consumer email accounts: jlipps, nick.mokhnach, and kazucocoa. The company-backed project makes the mixed account hygiene a minor concern, not evidence of limited maintenance capacity.
The top contributor made about 82% of the 11 recent commits, creating concentration risk. However, two additional contributors remained active and the repository is organization-owned, which partly compensates.
All 14 workflows were analyzed with no audit findings, unsafe checkouts, or script injections. However, all 43 action references are unpinned and three workflows grant top-level write permissions, creating workflow hygiene and token-scope concerns.
| Title | Versions | Severity |
|---|---|---|
CVE-2016-10557 appium-chromedriver is vulnerable to Missing Encryption of Sensitive Data in versions 0.0.0 - 2.9.4. | 0.0.0 - 2.9.4 | High |
| Dependency | Last Release | Score |
|---|---|---|
axios Version ^1.20.0 | — | — |
xpath Version ^0.x | — | — |
semver Version ^7.0.0 | — | — |
asyncbox Version ^6.4.3 | — | — |
appium-adb Version ^16.0.4 | — | — |
Connect your repositories to instantly see whether vulnerable or malicious packages exist in your codebase.
Free. No credit card required.

I consent to receiving marketing communications based on Aikido’s Privacy Policy.
SOC 2Compliant
ISO 27001Compliant
ISO 42001Compliant© All Intel data is openly available and commercially licensed.