amacrin

v0.0.1 suspicious
6.0
Medium Risk

Amacrin CLI — deploy and manage OSA archives on the Amacrin cloud platform

🤖 AI Analysis

Final verdict: SUSPICIOUS

The package shows high metadata risk due to suspicious repository activity and maintainer history, while other specific risks such as network, shell execution, obfuscation, and credential harvesting are relatively low.

  • High metadata risk
  • Potential supply-chain attack indicators
Per-check LLM notes
  • Network: The observed network calls suggest interaction with an external API, which could indicate legitimate functionality but also raises concerns about potential unauthorized data transfer.
  • Shell: No shell execution patterns were detected.
  • Obfuscation: No obfuscation patterns detected, suggesting low risk.
  • Credentials: No credential harvesting patterns detected, indicating low risk.
  • Metadata: High risk due to suspicious git repository activity and maintainer history.

📦 Package Quality Overall: Low (4.6/10)

✦ High Test Suite 9.0

Test suite present — 6 test file(s) found

  • 6 test file(s) detected (e.g. test_api.py)
◈ Medium Documentation 5.0

Some documentation present

  • Brief PyPI description (220 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

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

Single-author or unverifiable project

  • 1 unique contributor(s) across 1 commits in amacrin-labs/cli
  • Single author with few commits — possibly a personal or throwaway project

🔬 Heuristic Checks

⚠ Outbound Network Calls score 7.5

Found 5 network call pattern(s)

  • api_base(api_base) resp = httpx.post( f"{base}/archives", json=payload, h
  • _id={account_id}" resp = httpx.get(url, headers=_auth_headers(token), timeout=30.0) _handle
  • api_base(api_base) resp = httpx.get( f"{base}/archives/{archive_id}/status", hea
  • api_base(api_base) resp = httpx.post( f"{base}/archives/{archive_id}/deploy", jso
  • += "?force=true" resp = httpx.post(url, headers=_auth_headers(token), timeout=30.0) _handle
✓ 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: rory.bio>

✓ Suspicious Page Links

All external links appear legitimate

⚠ Git Repository History score 7.5

Git history flags: Repository has zero stars and zero forks

  • Repository has zero stars and zero forks
  • Very few commits: 1 total
  • Single contributor with only 1 commit(s) — possibly throwaway account
⚠ 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 amacrin 
Create a Python-based utility called 'AmacrinDeployer' that leverages the 'amacrin' package to streamline the deployment and management of OSA archives on the Amacrin cloud platform. This utility should provide a user-friendly interface for performing common tasks such as uploading new archives, updating existing ones, listing all deployed archives, and deleting obsolete files. Additionally, implement logging functionality to keep track of all actions performed through the utility. Ensure your application includes a comprehensive set of unit tests to validate its functionality.

Steps to follow:
1. Set up a virtual environment and install the 'amacrin' package.
2. Design the command-line interface for the utility, ensuring it accepts commands like 'deploy', 'update', 'list', and 'delete'.
3. Implement each command using the 'amacrin' package's API, making sure to handle errors gracefully.
4. Integrate logging to record each action taken by the utility.
5. Write unit tests for each feature to ensure reliability.
6. Document the setup process, usage instructions, and any dependencies.

Suggested Features:
- Support for specifying archive versions when deploying or updating.
- Option to schedule regular updates or deletions of archives.
- Integration with cloud storage services for automated backup of deployed archives.
- Ability to generate detailed reports on archive deployments.

By following these steps and incorporating the suggested features, you'll create a powerful tool for managing OSA archives on the Amacrin platform.

💬 Discussion Feed

Leave a comment

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