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

claudish-oai

v6.10.4

Published

Run Claude Code with any model - OpenRouter, Ollama, LM Studio & local models

Downloads

73

Readme

🔮 Claudish (OpenAI Path Fork)

Claude Code. Any Model. Custom Endpoints.

npm version license

A fork of Claudish with a small but critical fix for custom OpenAI-compatible providers.


What's Different?

This fork modifies the OpenAI provider's API path:

| | Original | This Fork | |--|----------|-----------| | API Path | /v1/chat/completions | /chat/completions |

Why?

Some OpenAI-compatible gateways and proxies don't use the /v1/ prefix in their endpoints. For example:

  • Kilo Gateway — custom routing without /v1/
  • Self-hosted proxies — simplified endpoint paths
  • Enterprise gateways — custom URL schemes

If you've ever seen errors like:

404 Not Found: /v1/chat/completions

...when your provider expects /chat/completions, this fork fixes that.

Installation

npm install -g claudish-oai

Usage

Same as upstream Claudish. Works with any OpenAI-compatible endpoint that uses /chat/completions:

# Set your custom base URL
export OPENAI_BASE_URL=https://your-gateway.example.com

# Run with any model
claudish --model gpt-4o "explain this code"

The Change

Single file modified: src/providers/provider-definitions.ts

- apiPath: "/v1/chat/completions"
+ apiPath: "/chat/completions"

That's it. One line. No other changes.


Based on Claudish by MadAppGang

Full documentation → claudish.com