Skip to main content

​
CLI

The Reposeek CLI is published as @reposeek/cli.

​
Requirements

  • Node.js >=18
  • Reposeek API key

​
Global install

​
Log in

reposeek login asks for an existing dashboard-created API key and stores it in your user-level Reposeek config directory. The key is not printed back to the terminal.

​
Authentication Patterns

​
Saved local login

reposeek login asks for an existing dashboard-created API key and stores it in your user-level Reposeek config directory. The key is not printed back to the terminal.

​
One-shot env var

Use this for CI, agents, and commands where you do not want to mutate local CLI state. REPOSEEK_API_KEY takes priority over saved credentials.

​
Local API base URL

Use this only when targeting a local or non-production API. REPOSEEK_API_BASE_URL takes priority over saved config for one process environment.

​
Auth Commands

auth status verifies the effective credential without consuming search quota. Running logout removes the saved local credential but does not revoke the dashboard API key.

​
Command

The CLI prints only the API response JSON unchanged on success: top-level request_id plus results with stars and forks. Response headers and timing are available to direct HTTP clients, not surfaced in CLI output. Quota-exhausted responses are printed to stderr as JSON and preserve error.usage.remaining_searches and error.usage.next_reset_at when the API returns those fields.