AI Analysis
The package exhibits high metadata risk due to recent creation and limited author details, which raises concerns about its legitimacy. However, other risk factors such as network, shell, obfuscation, and credential risks are low.
- High metadata risk
- Recent package and repository creation
- Single author version
- Missing author details
Per-check LLM notes
- Network: The observed network calls suggest legitimate authentication and token refresh mechanisms, which are common in many applications.
- Shell: No shell execution patterns were detected.
- Obfuscation: No obfuscation patterns detected, indicating low risk.
- Credentials: No credential harvesting patterns detected, indicating low risk.
- Metadata: High risk due to recent repository and package creation, single author version, and missing author details.
Heuristic Checks
Found 2 network call pattern(s)
d/auth/SignIn" response = httpx.post( url, json={"userName": credentials.user_nam/RefreshToken" response = httpx.get( url, headers={"Authorization": f"Bearer {cu
No obfuscation patterns detected
No shell execution patterns detected
No credential harvesting patterns detected
No typosquatting candidates detected
Email domain looks legitimate: gmail.com>
All external links appear legitimate
Git history flags: Repository created very recently: 0 day(s) ago (2026-06-05T00:43:45Z)
Repository created very recently: 0 day(s) ago (2026-06-05T00:43:45Z)All 7 commits happened within 24 hours
4 maintainer concern(s) found
Only one version has ever been released — brand new packagePackage uploaded less than 24 hours ago (2026-06-05T02:13:01.000Z)Author name is missing or very shortAuthor "" appears to have only 1 package on PyPI (new or inactive account)
💬 Discussion Feed
No discussion yet. Be the first to share your thoughts!
Report Abuse / Security Issue