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

sloproxy

v0.8.0

Published

Single Local Origin Proxy for routing OpenAI-compatible inference to models running on your own machine.

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Git

Maintainers

mattwiebemattwiebe

Keywords

Readme

SLOProxy

SLOProxy is the Single Local Origin Proxy: a small Node.js CLI for routing OpenAI-compatible inference requests to models running on your own machine.

It can front one or more localhost backends such as Ollama, LM Studio, llama.cpp, vLLM, or another OpenAI-compatible server. It can stay local-only, or expose the same local origin through Tailscale Funnel or Cloudflare Tunnel.

Install

npm install -g sloproxy

Then initialize and run the proxy:

sloproxy init
sloproxy up

You can also run it without a global install:

npx sloproxy init
npx sloproxy up

Commands

sloproxy up
sloproxy init
sloproxy install
sloproxy start
sloproxy stop
sloproxy status
sloproxy rotate-key
sloproxy uninstall

On macOS, sloproxy install writes a LaunchAgent at ~/Library/LaunchAgents/com.mattwiebe.sloproxy.plist so the proxy can run in the background across logins.

Configuration

Guided setup will:

  • scan common localhost ports for OpenAI-compatible providers,
  • ask for provider slugs and ports that were not detected,
  • ask whether to run local-only, Tailscale Funnel, or Cloudflare Tunnel,
  • generate or accept an API key for tunneled modes,
  • save configuration to ~/.config/sloproxy/.env.

The persisted .env uses this provider format:

PORT="13531"
TUNNEL_MODE="local"
PROVIDERS="ollama:11434,lmstudio:1234"
API_KEY=""

The running proxy watches its .env file and restarts itself when that file changes.

Providers

Configured providers are exposed as one OpenAI-compatible endpoint. The proxy prefixes model IDs with the provider slug in /v1/models, for example ollama/llama3.2 or lmstudio/local-model. Requests should send that prefixed model ID; SLOProxy strips the slug before forwarding to the matching local provider.

Provider slugs and ports must both be unique. If two providers use the same localhost port, startup fails with a configuration error instead of guessing which provider owns that port.

Examples

sloproxy up --port 13531
sloproxy up --provider ollama:11434 --provider lmstudio:1234
sloproxy up --tunnel cloudflare
sloproxy up --tunnel tailscale
sloproxy up --funnel-port 10000
sloproxy up --backend http://localhost:11434
sloproxy up --api-key your-secret
sloproxy up --no-tunnel

Development

npm ci
npm run lint
npm test

This project is independent from the WordPress plugin that recommends it.