🤖 AI Analysis

Final verdict: SUSPICIOUS

The package shows low risks in network, shell, obfuscation, and credential areas but raises suspicion due to its new upload status and lack of maintainer history.

Lacks maintainer history
No author name provided

Per-check LLM notes

Network: Network calls are expected for cloud-related packages to interact with remote services, but specific behavior should be reviewed.
Shell: No shell execution patterns detected, which is normal and indicates lower risk.
Obfuscation: No obfuscation patterns detected, indicating low risk of malicious activity.
Credentials: No credential harvesting patterns detected, indicating low risk of secret theft.
Metadata: The package is newly uploaded with no maintainer history and lacks an author name, raising suspicion.

🔬 Heuristic Checks

⚠ Outbound Network Calls score 1.5

Found 1 network call pattern(s)

existing_headers return httpx.AsyncClient(**kwargs) def build_environment_class( *, base_env

✓ 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

No author email provided

✓ Suspicious Page Links

All external links appear legitimate

✓ Git Repository History

No GitHub repository linked

No GitHub repository link found

⚠ Maintainer History score 10.0

5 maintainer concern(s) found

Only one version has ever been released — brand new package
Package uploaded less than 24 hours ago (2026-06-05T01:25:24.000Z)
Author name is missing or very short
Author "" appears to have only 1 package on PyPI (new or inactive account)
Package has no PyPI classifiers (low effort / metadata quality)