npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

pi-provider-gd

v1.3.0

Published

Native `gd` pi provider for provider.girard-davila.net (gd API served from api.girard-davila.net): /login gd accepts a pasted API key or browser SSO, key auto-stored, models appear as gd/<model-id> with no restart. Self-contained (no pi-provider-litellm).

Readme

pi-provider-gd

A native pi gd provider for provider.girard-davila.net

pi install npm:pi-provider-gd
/login gd
/model

Features

  • Self-contained — pi-provider-gd registers its own native pi provider (createProvider + OpenAI-compatible streaming from @earendil-works/pi-ai).
  • Native /login gd — API key only: sign in with Google at https://provider.girard-davila.net/auth/google, copy the issued API key from your dashboard at https://provider.girard-davila.net/, and paste it. Pi stores the key in ~/.pi/agent/auth.json under gd. No manual key handling.
  • gd/<model-id> — models surface under the gd provider id in /model and /login, refreshed live from the proxy's /v1/models. No pi restart needed.
  • Sensible default model — a new session with no model selected automatically lands on the default gd model (first live model, or GD_DEFAULT_MODEL if you set it) once a credential exists. No "no model" dead-end after install + login.
  • Honest failures — if the proxy is unreachable or the key is rejected, /model refresh surfaces an error ("model discovery request failed … check network connectivity to the proxy") instead of silently showing zero models.
  • /gd-doctor — in-pi diagnostics: shows the exact cause when a catalog refresh fails (credential state, network error, HTTP status, model list), since pi's /model screen hides the underlying error.
  • OpenAI-compatible streaming — requests go to the gd API at https://api.girard-davila.net/api/llm/v1/chat/completions with tool-call, thinking, and streaming support via pi-ai's openai-completions transport.
  • Fallbacks — GD_API_KEY env var is honored as an ambient credential; re-running /login gd resumes.
  • GPU overflow control — /gd-gpu-on [params] / /gd-gpu-off [instance_id] / /gd-gpu status, gd_deploy_gpu/gd_gpu_model tools, and a live [gd <ledger €> ●● <burn €/h>] powerline footer (/gd-footer on). See below.

GPU overflow: /deploy-gpu + powerline footer

The proxy's dedicated GPU is primary; a rented VAST.ai 3090 is the overflow ("slow mode"), routed through the same LiteLLM group. This package drives the rental end-to-end:

  • /deploy-gpu [max $/hr] (prompt template) — checks the gd VAST user's money (balance and credit — either one pays), reuses a running instance or launches one via vast/scripts/launch.py (datacenter-only by default; a cold launch takes 10–20 min including the model download), waits until the model is loaded, then switches this pi session to gd/qwen3.8-primary — the LiteLLM group that includes the VAST overflow row — and finishes. A settle beep (pi-beep) marks readiness.
  • gd_deploy_gpu / gd_gpu_model — the same as tools, for agents.
  • /gd-gpu-on [standard|premium] [--price <max $/hr>] [--home-ok] — creates a VAST GPU instance with sensible defaults (datacenter-only, no price cap = top candidate rate, reuses a running instance, $1.00 min-balance floor). Tier: standard = RTX 3090 24 GB (default, $VAST_TIER wins), premium = RTX 5090 32 GB. Runs detached (10–20 min) and messages back when READY. --home-ok is a test-only override allowing non-datacenter hosts.
  • /gd-gpu-off [instance_id] — destroys the instance (stops billing) and blocks the litellm VAST row (down first). No id = the current instance from state/label.
  • /gd-gpu — status: ledger money, VAST account (balance + credit), running instances with burn rate, local state, and what the footer is showing.

Powerline footer segment (via the bundled pi-powerline-footer dependency, referenced in package.json pi.extensions as ./node_modules/pi-powerline-footer/index.ts) — run /gd-footer on once; the bar then shows, e.g.:

Note: after upgrading pi-provider-gd, run pi update --extensions (or pi remove + pi install npm:pi-provider-gd) so the pi-powerline-footer dependency is installed into node_modules, then /reload. Without the dependency's extension loaded, /gd-footer writes the customItems entry but nothing renders.

gd my-key 8.22€ ● 0.23€/h
gd my-key -0.00€ ●● 0.68€/h
gd my-key 8.22€ !
  • name = the key name you filled in on the provider.girard-davila.net dashboard (LiteLLM key_alias from the same /key/info call as the ledger), truncated to 14 chars. Shown first, before the money.
  • money = the provider.girard-davila.net ledger of your gd customer key, the same number your dashboard shows: budget − spend when a budget is set (red under 10%), or −spend in grey when the key has no budget. Never raw VAST funds. (Technically it is read from the proxy's key record — budget, spend — but the ledger is yours, on the portal.)
  • ● per VAST GPU — the dot tracks the GPU readiness lifecycle: yellow = launch started, waiting for a GPU (offer/creation); grey = instance up, model downloading/loading; green = ready (model loaded, serving); red = last launch failed (or the failed instance is still running and billing). Multiple servers: dots and burn aggregate over all running VAST instances, plus synthetic dots for waiting/failed states driven by state/launching.json and state/last_failure.json.
  • burn = summed $/h of the running instances; turns red when a burn alert is active.
  • burn alerts (read-only, they never tear anything down):
    • ⏱x.xh (red) = the tracked instance has been rented for ≥ 3 h (uptime from state/current.json launched_at).
    • ⚠x.xh (red) = remaining VAST money (balance + credit) buys less than one workday of work at the current burn: money ÷ (burn × GD_DAY_HOURS) < 1. GD_DAY_HOURS defaults to 8, env-overridable. The number is hours of work left.
  • ! (red) = last refresh failed (stale data still shown if any).

/gd-footer off|status manage it; the entry is powerline.customItems in ~/.pi/agent/settings.json (id gd-gpu, selfColorize). Polling is 30 s, best-effort, and silent when no VAST/ledger credentials are present.

Install

pi install npm:pi-provider-gd

That's the only step. Restart pi (or /reload) if you installed it mid-session.

Log in

Run /login gd in pi's interactive mode and pick provider.girard-davila.net. Sign in with Google at https://provider.girard-davila.net/auth/google, copy the issued API key from your dashboard, and paste it. The key appears stored in the terminal. Then:

/model

Pick any gd/<model-id>.

A brand-new session that has no model yet is pointed at the default gd model automatically (default qwen3.8-primary, override with the GD_DEFAULT_MODEL env var, validated against the live catalog). If pi reports that the model catalog could not be refreshed (Could not refresh gd; showing cached models), run /gd-doctor in pi — it reports the exact cause (missing credential, network failure, HTTP error, or the model list), since pi's /model screen hides the underlying error. As a shell check, verify the machine can reach the proxy at all:

curl -I https://api.girard-davila.net/api/llm/v1/models   # API host (machine-to-machine), not the portal

A failure there means a connectivity/VPN problem on that machine, not a pi problem. /gd-doctor includes the exact failure and a contact for the maintainer (Alexandre Girard, [email protected]) — include its output when reporting a problem.

How it works

  • extensions/index.ts registers one native provider: createGdProvider() → pi.registerProvider(...), and on session_start lands model-less sessions on the default gd model when a credential is stored.
  • src/provider.ts builds the provider with createProvider (pi-ai) + openAICompletionsApi(); auth.apiKey.login asks for the API key issued after Google sign-in at provider.girard-davila.net/auth/google, fetchModels polls /v1/models with the resolved key (strict: network/auth failures surface as refresh errors; limits lookup stays best-effort).
  • src/core.ts holds the pure, testable logic: SSO start/poll (/sso/cli/start, /sso/cli/poll/{id} with the x-litellm-cli-poll-secret header), model listing, auth.json read/store.
  • src/gpu.ts holds the VAST orchestration: balance gate (decideBalance — balance or credit pays), running-instance reuse, scripts.launch spawn with progress, READY from state/current.json. src/gpu-status.ts holds the footer: ledger lookup (/key/info), instance polling (v1 API), and the ANSI formatGdStatus renderer. Keys come from vast/config.env (VAST_API_KEY, LITELLM_OPS_KEY) next to the launcher.
  • Credentials live in ~/.pi/agent/auth.json under gd — the same file pi uses for every provider.

Testing

npm install
npm test          # node --test, hermetic (globalThis.fetch stubbed)
npx tsc --noEmit  # type-check src + extension + tests

CI (.github/workflows/ci.yml) runs both on every push/PR.

Endpoint

Everything a customer touches is on provider.girard-davila.net:

  • Dashboard, spend ledger and credit top-ups: https://provider.girard-davila.net/
  • Sign-in: https://provider.girard-davila.net/auth/google

Model traffic goes to the gd API host (infrastructure, no UI):

  • Proxy root: https://api.girard-davila.net/api/llm (OpenAI-compatible /v1/*), overridable with GD_BASE_URL for farm/LAN setups
  • API-key top-ups from inside pi (/gd-pay) call https://provider.girard-davila.net/billing, overridable with GD_BILLING_URL

License

MIT