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

@openenthrium/oe-runtime-sdk

v1.7.5

Published

OE Runtime SDK — embed AI agent execution directly in your Node.js application. Same engine as OE Runtime CLI, importable as a library.

Readme

OE Runtime SDK

Embed AI agent execution directly in your Node.js application. Same engine as OE Runtime CLI — no subprocess, no HTTP overhead, just a function call.

Install

npm install @openenthrium/oe-runtime-sdk

Install only the connector dependencies your agents actually use:

# PostgreSQL / MySQL / SQLite
npm install pg          # PostgreSQL
npm install mysql2      # MySQL / MariaDB
npm install better-sqlite3  # SQLite

# MongoDB
npm install mongodb

# Redis
npm install ioredis

# Kafka / RabbitMQ
npm install kafkajs

# S3 / object storage
npm install @aws-sdk/client-s3

# SSH
npm install ssh2

# Gmail / Google Drive
npm install googleapis

Usage

From file paths

const { runAgent } = require("@openenthrium/oe-runtime-sdk");

const result = await runAgent(
  "./agent.yaml",       // path to your agent
  "./oe-config.json",   // path to your config
  { topic: "Q3 sales" } // optional params
);

console.log(result.output);
console.log(result.toolCalls); // list of connector tools called

From objects (no file I/O)

const { runAgentFromObject } = require("@openenthrium/oe-runtime-sdk");

const agent = {
  name: "Database Analyst",
  instructions: "You are a SQL analyst.",
  steps: [{ name: "Query", content: "List all tables and their row counts." }],
  connectors: [{ connection_name: "My Database", connection_type: "postgresql" }],
};

const config = {
  llm: { provider: "openai", model: "gpt-4o", apiKey: "sk-..." },
  connectors: [{
    connection_name: "My Database",
    connection_type: "postgresql",
    host: "localhost", port: 5432,
    database: "mydb", user: "postgres", password: "secret"
  }]
};

const result = await runAgentFromObject(agent, config, {});
console.log(result.output);

With hooks (streaming tool calls)

const { runAgent } = require("@openenthrium/oe-runtime-sdk");

const result = await runAgent("./agent.yaml", "./oe-config.json", {}, {
  onToolCall:   (name)         => console.log(`→ ${name}`),
  onToolResult: (name, result) => console.log(`↳ ${result}`),
  onDone:       (output)       => console.log("Done:", output),
  onError:      (err)          => console.error("Error:", err),
});

Config file format

Same oe-config.json used by OE Runtime CLI — no changes needed:

{
  "llm": {
    "provider": "openai",
    "model": "gpt-4o",
    "apiKey": "YOUR_OPENAI_API_KEY"
  },
  "server": {
    "enabled": false,
    "port": 3333,
    "apiKey": "your-secret-api-key"
  },
  "connectors": [
    {
      "connection_name": "My Database",
      "connection_type": "postgresql",
      "host": "localhost",
      "port": 5432,
      "database": "mydb",
      "user": "postgres",
      "password": "YOUR_DB_PASSWORD"
    }
  ]
}

Supported LLM providers

OpenAI, Anthropic, Azure OpenAI, Groq, Mistral, Ollama, Google Gemini, AWS Bedrock, and any OpenAI-compatible endpoint.

Supported connectors

30+ connector types — PostgreSQL, MySQL, MongoDB, Redis, Elasticsearch, S3, GitHub, Slack, Gmail, Jira, Confluence, Notion, HubSpot, Kafka, MQTT, LDAP, GraphQL, Web3/Blockchain, SSH, shell, SFTP, and more.

See OE Runtime Connector Catalog for the full list.

Links