allocation

v0.0.1 suspicious
5.0
Medium Risk

Online (streaming) portfolio construction: scikit-learn / skfolio-compatible estimators over a keyed dynamic universe

🤖 AI Analysis

Final verdict: SUSPICIOUS

The package shows no immediate signs of malicious activity such as network calls or shell executions, but its metadata suggests recent and rapid development which raises concerns about potential supply-chain attacks.

  • Metadata risk score of 7 out of 10 due to recent and rapid commits
  • Lack of historical development context increases suspicion
Per-check LLM notes
  • Network: No network calls detected, which is normal unless the package's functionality requires external communication.
  • Shell: No shell execution detected, reducing the risk of malicious code execution.
  • Obfuscation: No obfuscation patterns detected, indicating low risk.
  • Credentials: No credential harvesting patterns detected, indicating low risk.
  • Metadata: The repository and package are very new, with all commits happening within a short period, raising suspicion of potential malicious intent.

🔬 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: microprediction.com>

Suspicious Page Links

All external links appear legitimate

Git Repository History score 5.0

Git history flags: Repository created very recently: 0 day(s) ago (2026-06-05T02:09:09Z)

  • Repository created very recently: 0 day(s) ago (2026-06-05T02:09:09Z)
  • All 9 commits happened within 24 hours
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-05T04:58:38.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)