avp-wallet-sdk

v0.4.0 suspicious
6.0
Medium Risk

Python client for the AVP Agent Verification Protocol — multi-chain wallet trust scoring

🤖 AI Analysis

Final verdict: SUSPICIOUS

The package shows minimal risk indicators such as no network calls or shell executions. However, the metadata risk score is elevated due to low maintainer history and insufficient details, raising suspicion about its legitimacy.

  • Metadata risk score of 7 out of 10 due to repository's recent activity pattern and lack of detailed maintainer history.
  • No other significant risks detected.
Per-check LLM notes
  • Network: No network calls detected, which is normal if the package does not require external API interactions.
  • Shell: No shell execution patterns detected, indicating no immediate signs of executing system commands.
  • Obfuscation: No obfuscation patterns detected, suggesting legitimate use without risk of code hiding.
  • Credentials: No credential harvesting patterns detected, indicating safe handling of sensitive information.
  • Metadata: The repository's recent activity pattern, low maintainer history, and lack of details raise concerns about potential malicious intent.

📦 Package Quality Overall: Low (4.4/10)

◈ Medium Test Suite 6.0

Partial test coverage signals detected

  • 1 test file(s) detected (e.g. test_client.py)
◈ Medium Documentation 7.0

Some documentation present

  • Documentation URL: "Documentation" -> https://avp-protocol.onrender.com/docs
  • Detailed PyPI description (3712 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

  • 12 type-annotated function signatures detected in source
○ Low Multiple Contributors 2.0

Single-author or unverifiable project

  • 1 unique contributor(s) across 9 commits in ABICITYE/avp-protocol
  • Single author with few commits — possibly a personal or throwaway project

🔬 Heuristic Checks

✓ Outbound Network Calls

No suspicious network call patterns found

✓ Code Obfuscation

No obfuscation patterns detected

✓ Shell / Subprocess Execution

No shell execution patterns detected

✓ Credential Harvesting

No credential harvesting patterns detected

✓ Typosquatting

No typosquatting candidates detected

✓ Registered Email Domain

Email domain looks legitimate: gmail.com>

✓ Suspicious Page Links

All external links appear legitimate

⚠ Git Repository History score 5.0

Git history flags: Repository has zero stars and zero forks

  • Repository has zero stars and zero forks
  • All 9 commits happened within 24 hours
⚠ 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 avp-wallet-sdk 
Develop a fully-functional mini-application that utilizes the 'avp-wallet-sdk' Python package to create a user-friendly interface for managing and evaluating trust scores of wallets across multiple blockchain networks. Your application should allow users to input their wallet addresses from various chains (e.g., Ethereum, Binance Smart Chain), and then fetch and display their trust scores based on the AVP Agent Verification Protocol.

Step-by-step guide:
1. Set up a basic Flask web framework to serve as the backend for your application.
2. Integrate the 'avp-wallet-sdk' package into your project by installing it via pip.
3. Create a RESTful API endpoint that accepts POST requests containing wallet addresses.
4. Within the API endpoint, use the 'avp-wallet-sdk' to query the trust score for each provided wallet address.
5. Design a simple front-end using HTML/CSS/JavaScript to interact with the backend API.
6. Implement form validation on the front-end to ensure only valid wallet addresses are submitted.
7. Display the fetched trust scores in a readable format, along with any additional information provided by the SDK such as verification status or recent activity.
8. Add error handling to manage cases where a wallet address is invalid or not supported by the protocol.
9. Consider implementing caching mechanisms to improve performance when fetching scores for frequently requested wallets.
10. Finally, document your code thoroughly and include instructions on setting up the environment and running the application.

💬 Discussion Feed

Leave a comment

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