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

@oml/server

v0.26.1

Published

Standalone OML server host

Readme

@oml/server

Standalone OML server runtime package.

The only user-facing CLI is oml from @oml/cli. Use oml server start, oml server stop, and oml server status to manage the server.

Options

  • --host, -h: bind host. Default: 127.0.0.1
  • --port, -p: bind port. Default: 8080
  • --workspace, -w: workspace root used to initialize the server. Default: current working directory
  • --token: bearer token required for REST endpoints (except /health)
  • --refresh-token: optional refresh token used by server auth refresh
  • --token-expires-at: optional access-token expiration time (epoch ms)

Canonical CLI

From a local checkout:

node packages/cli/bin/cli.js server start

When installed from npm:

oml server start

Server management commands:

oml server start
oml server status
oml server stop

If the requested port is already occupied, startup fails immediately with a clear message naming the occupied host and port.

REST API

The server exposes only these endpoints:

  • GET /health
  • GET /openapi.json
  • GET /v0/models
  • POST /v0/query
  • POST /v0/update
  • POST /v0/fuzzysearch
  • POST /v0/lint
  • POST /v0/reason
  • POST /v0/validate
  • POST /v0/render
  • POST /v0/export

Health check:

curl http://127.0.0.1:8080/health

Run a SPARQL query:

curl -X POST http://127.0.0.1:8080/v0/query \
  -H 'content-type: application/json' \
  -d '{
    "modelUri": "file:///absolute/path/to/model.oml",
    "sparql": "SELECT * WHERE { ?s ?p ?o } LIMIT 10"
  }'

Run update request:

curl -X POST http://127.0.0.1:8080/v0/update \
  -H 'content-type: application/json' \
  -d '{
    "operations": [
      {
        "createInstance": {
          "descriptionIri": "https://example.com/demo#",
          "instanceName": "alice"
        }
      }
    ]
  }'

Run fuzzy search:

curl -X POST http://127.0.0.1:8080/v0/fuzzysearch \
  -H 'content-type: application/json' \
  -d '{
    "text": "firefighter",
    "limit": 10
  }'