autowsgr

v2.2.2 suspicious
4.0
Medium Risk

Auto Warship Girls Framework.

🤖 AI Analysis

Final verdict: SUSPICIOUS

The package shows signs of potential obfuscation and has incomplete metadata, raising concerns about its integrity.

  • Non-English comments and unusual use of eval()
  • Missing maintainer's author name and potentially inactive account
Per-check LLM notes
  • Network: No network calls detected.
  • Shell: Shell executions are likely related to managing an ADB server, which is typical for packages dealing with Android development or testing.
  • Obfuscation: The presence of non-English comments and unusual use of eval() suggests potential obfuscation, but without more context, it's hard to determine if it's malicious.
  • Credentials: No suspicious patterns for credential harvesting were detected.
  • Metadata: The maintainer's author name is missing and the account seems new or inactive, which raises some concern but does not strongly indicate malicious intent.

📦 Package Quality Overall: Medium (6.0/10)

◈ Medium Test Suite 6.0

Partial test coverage signals detected

  • Test runner config found: pyproject.toml
◈ Medium Documentation 7.0

Some documentation present

  • Documentation URL: "Documentation" -> https://docs-autowsgr.notion.site
  • Detailed PyPI description (2244 chars)
○ Low Contributing Guide 2.0

No contributing guide or governance files found

  • No CONTRIBUTING, CODE_OF_CONDUCT, or governance files found
◈ Medium Type Annotations 5.0

Partial type annotation coverage

  • 204 type-annotated function signatures detected in source
✦ High Multiple Contributors 10.0

Active multi-contributor project

  • 11 unique contributor(s) across 100 commits in OpenWSGR/AutoWSGR
  • Active community — 5 or more distinct contributors

🔬 Heuristic Checks

✓ Outbound Network Calls

No suspicious network call patterns found

⚠ Code Obfuscation score 4.0

Found 2 obfuscation pattern(s)

  • 战斗。""" """安全规则引擎 — 替代旧代码中的 ``eval()``。 旧代码使用类似 ``eval("(BB >= 2) and (CV > 0)")`` 的方式在运行时判断敌方
  • 代旧代码中的 ``eval()``。 旧代码使用类似 ``eval("(BB >= 2) and (CV > 0)")`` 的方式在运行时判断敌方编成， 存在代码注入风险。本模块提供结构化
⚠ Shell / Subprocess Execution score 10.0

Found 6 shell execution pattern(s)

  • b() try: result = subprocess.run( # noqa: S603 [adb, 'devices'], cap
  • ALS: try: subprocess.run( # noqa: S603 [adb, 'connect', serial],
  • adb = _find_adb() subprocess.run([adb, 'kill-server'], timeout=5, capture_output=True, check=
  • time.sleep(1) subprocess.run([adb, 'start-server'], timeout=8, capture_output=True, check
  • alse try: subprocess.run( # noqa: S603 ['pgrep', '-f', self._process
  • 置）') try: subprocess.Popen(shlex.split(self._path)) # noqa: S603 _log.info
✓ Credential Harvesting

No credential harvesting patterns detected

✓ Typosquatting

No typosquatting candidates detected

✓ Registered Email Domain

No author email provided

✓ Suspicious Page Links

All external links appear legitimate

✓ Git Repository History

Repository OpenWSGR/AutoWSGR appears legitimate

⚠ Maintainer History score 4.0

2 maintainer concern(s) found

  • 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 autowsgr 
Create a fully-functional mini-app that serves as a Warship Girls game companion. This app will utilize the 'autowsgr' package to interact with the game's API, providing players with real-time updates on their fleets, missions, and other game-related information. Here are the key steps and features of the project:

1. **Setup Environment**: Begin by setting up your Python environment. Ensure you have Python installed, then install the 'autowsgr' package via pip.
2. **Authentication Module**: Implement an authentication module using 'autowsgr'. This module should allow users to log into their Warship Girls accounts securely, fetching necessary tokens or credentials to access the game's API.
3. **Data Retrieval**: Use 'autowsgr' to retrieve data about the player's fleets, including ship status, equipment details, and crew members. Additionally, fetch mission statuses and rewards from ongoing quests.
4. **Real-Time Updates**: Integrate functionality that provides real-time updates for missions and fleet statuses. Users should receive notifications when ships are ready for battle or when missions complete.
5. **User Interface**: Develop a simple yet intuitive user interface (UI) where users can view their fleet status, mission progress, and other relevant information. Consider using a web framework like Flask or Django for backend services and a frontend framework like React or Vue.js.
6. **Customization Options**: Allow users to customize alerts and notifications based on their preferences. For example, they might want to receive alerts only for certain types of ships or specific mission completions.
7. **Analytics Dashboard**: Create an analytics dashboard within the app that tracks performance metrics such as win rates, battle outcomes, and resource usage over time.
8. **Integration Testing**: Test all functionalities of the app thoroughly, ensuring smooth interaction with the 'autowsgr' package and accurate retrieval and display of data.
9. **Deployment**: Once testing is successful, deploy the app to a server or cloud platform of your choice, making it accessible to Warship Girls players worldwide.

By following these steps and utilizing the capabilities provided by the 'autowsgr' package, you'll create a valuable tool for Warship Girls enthusiasts looking to enhance their gaming experience.

💬 Discussion Feed

Leave a comment

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