android-avd-cli

v0.1.0 suspicious
5.0
Medium Risk

Android Emulator AVD CLI — manage emulators, grant root, run ADB commands

🤖 AI Analysis

Final verdict: SUSPICIOUS

The package shows signs of being legitimate but raises some red flags, particularly regarding metadata and obfuscation techniques.

  • metadata risk due to lack of repository and incomplete maintainer profile
  • use of obfuscation techniques that could indicate an attempt to evade detection
Per-check LLM notes
  • Network: No network calls detected, which is normal and expected.
  • Shell: Shell execution is primarily used for interacting with the Android Debug Bridge (ADB) to manage AVDs. This is consistent with the package's expected functionality.
  • Obfuscation: The code uses obfuscation techniques such as importing modules using __import__ and splitting lines to make static analysis harder, but it does not appear to be malicious.
  • Credentials: No patterns indicative of credential harvesting were detected.
  • Metadata: The repository is not found, the maintainer has limited history and an incomplete profile, raising concerns about potential malicious intent.

📦 Package Quality Overall: Low (3.6/10)

○ Low Test Suite 1.0

No test suite detected

  • No test files or test-runner configuration detected
◈ Medium Documentation 7.0

Some documentation present

  • Documentation URL: "Documentation" -> https://github.com/overtimepog/android-cli#readme
  • Detailed PyPI description (3071 chars)
○ Low Contributing Guide 4.0

No contributing guide or governance files found

  • Development Status classifier >= Beta
◈ Medium Type Annotations 5.0

Partial type annotation coverage

  • 25 type-annotated function signatures detected in source
○ Low Multiple Contributors 1.0

Could not retrieve contributor data from GitHub

  • GitHub API error: 404

🔬 Heuristic Checks

✓ Outbound Network Calls

No suspicious network call patterns found

⚠ Code Obfuscation score 10.0

Found 6 obfuscation pattern(s)

  • print("ADB not found", file=__import__("sys").stderr) return None if not cmd: return
  • t(result.stderr.strip(), file=__import__("sys").stderr) return result.stdout except subprocess.
  • hell command timed out", file=__import__("sys").stderr) return None except FileNotFoundError:
  • ry not found at: {adb}", file=__import__("sys").stderr) return None def device_info( avd_name
  • version=f"android-cli {__import__('android_cli').__version__}", ) parser.add_argument( "--sd
  • ry not found at: {emu}", file=__import__("sys").stderr) return False def kill_avd( avd_name:
⚠ Shell / Subprocess Execution score 10.0

Found 6 shell execution pattern(s)

  • )] try: result = subprocess.run( [adb, "shell"] + shell_cmd, capture
  • try: result = subprocess.run( [adb, "shell", "getprop", prop],
  • tus try: result = subprocess.run( [adb, "shell", "which", "su"], capt
  • n" try: result = subprocess.run( [adb, "shell", "su", "-v"], capture
  • [] try: result = subprocess.run( [adb, "devices"], capture_output=Tr
  • ator_binary(sdk) result = subprocess.run( [emu, "-list-avds"], capture_output=True, text=True
✓ Credential Harvesting

No credential harvesting patterns detected

✓ Typosquatting

No typosquatting candidates detected

✓ Registered Email Domain

Email domain looks legitimate: users.noreply.github.com>

✓ Suspicious Page Links

All external links appear legitimate

⚠ Git Repository History score 3.0

Repository not found (deleted or private)

  • Repository not found (deleted or private)
⚠ Maintainer History score 6.0

3 maintainer concern(s) found

  • Only one version has ever been released — brand new package
  • Author name is missing or very short
  • Author "" appears to have only 1 package on PyPI (new or inactive account)
✓ Known CVE Vulnerabilities

No known vulnerabilities found in OSV database.

💡 AI App Starter Prompt

Use this prompt to build a project with android-avd-cli 
Create a command-line tool named 'AVDManager' that leverages the 'android-avd-cli' package to streamline the management of Android Virtual Devices (AVDs). This tool should allow users to easily perform various operations such as listing available AVDs, starting and stopping AVDs, checking the status of AVDs, granting root access, and executing ADB commands directly from the command line interface. Additionally, consider integrating features like saving and restoring AVD configurations, setting up custom AVDs with specific hardware profiles, and automating routine tasks like backup and restore processes. The application should provide clear and concise output, and include error handling for common issues such as invalid commands or missing dependencies. Utilize the 'android-avd-cli' package to handle all interactions with AVDs, ensuring that your tool remains lightweight and efficient.

💬 Discussion Feed

Leave a comment

No discussion yet. Be the first to share your thoughts!