Local LLM cost proxy: forecasts each call and recommends the cheapest model that clears the task.
Inferred from the transports this listing declares (stdio). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.
Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.
The published package tarball could not be read at scan time (no sdist), so no tool declarations could be extracted from it. Nothing here is a statement about what this exposes.
Local LLM cost proxy: forecasts each call and recommends the cheapest model that clears the task.
Forge's dependency resolver reads npm metadata only, so this PyPI package has no resolved tree. That is a gap in coverage, not a clean bill of health.