midscene-android-automation@1.0.3
CAUTION· static onlyPublisher claims: "Vision-driven Android device automation using Midscene. Operates entirely from screenshots — no DOM or accessibility labels required. Can interact with all v..." Observed in sandbox: static analysis only — behavior not yet observed.
Coverage
Static only; nothing was run yet.The label rests on the code, the instruction files and the publisher. The honeypot run replaces this verdict when it completes.
Is [email protected] safe to install?
KillerSkills analysed it statically (a sandbox run is pending) on 2026-11-18 and scored it 63/100 (Caution). It is not known to be malicious, but it has behaviour or code a security policy should decide on before install. Notable findings: Access to sensitive file paths; Access to sensitive file paths. Summary: static analysis only — behavior not yet observed.
Behavior trace
Queued for honeypot run · static analysis onlyThis version has not been detonated yet. The score above counts behavior as unknown (50/100), so it cannot read Verified until the honeypot run completes and replaces this verdict.
Static findings
Automate Android devices using `npx -y @midscene/android@1`. Each CLI command maps directly to an MCP tool — you (the AI agent) act as the brain, deciding which actions to take based on screenshots.Fix: Pin versions and sources; vendor anything fetched at install time.… variables must be configured — either as system environment variables or in a `.env` file in the current working directory (Midscene loads `.env` automatically): …Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.| **API key error** | Check `.env` file contains `MIDSCENE_MODEL_API_KEY=<your-key>`. See [Model Configuration](https://midscenejs.com/zh/model-common-config.html). |Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.npx -y @midscene/android@1 connectFix: Pin versions and sources; vendor anything fetched at install time.npx -y @midscene/android@1 connect --deviceId emulator-5554Fix: Pin versions and sources; vendor anything fetched at install time.npx -y @midscene/android@1 launch --uri https://www.ebay.comFix: Pin versions and sources; vendor anything fetched at install time.npx -y @midscene/android@1 launch --uri com.android.settingsFix: Pin versions and sources; vendor anything fetched at install time.…ene/core version`, and `npm view @midscene/shared version`. Upgrade as needed (`npm i @midscene/android@latest @midscene/core@latest @midscene/shared@latest`). | | **Wrong device targeted** …Fix: Pin the exact version (`[email protected]`, `==1.2.3`) so every install gets the bytes that were reviewed.Cost to the agent
Tokens estimated at four characters each. Skills load their instruction text when triggered; the figure is what that costs.
Known vulnerabilities
Vulnerability advisories (OSV) cover npm and PyPI packages; this registry has no advisory database.
What would make this Verified
17 points to 80 · weights: behavior 45%, static 25%, prompt 15%, publisher 15%- Unclaimed publisher≈ +8 on the totalClaim quanru: a verified publisher gets +50 on publisher trust. It is free and usually instant with GitHub sign-in.
- Access to sensitive file paths≈ +4 on the totalStop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
- npx invocation of non-well-known package≈ +2 on the totalPin versions and sources; vendor anything fetched at install time.
- Unpinned dependencies≈ +1 on the totalPin exact versions (and ideally hashes) in package.json, requirements or the install script so the bundle cannot change under you.
- Unpinned dependency≈ +1 on the totalPin the exact version (`[email protected]`, `==1.2.3`) so every install gets the bytes that were reviewed.