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

@tramo/server

v0.2.5

Published

Long-running host for tramo workflows — webhooks, cron, a management API, durable runs, and human-in-the-loop approvals.

Readme

@tramo/server

The long-running host for tramo workflows. It loads a catalog of workflows and:

  • serves webhook endpoints (with HMAC verification),
  • fires cron triggers on schedule (cron syntax or natural language),
  • exposes a JSON management API,
  • records run history with token/cost stats,
  • persists suspended runs and resumes them on an approval decision,
  • writes an optional audit trail and redacts secrets everywhere.

Quick start (programmatic)

import { createTramoServer } from '@tramo/server';
import { combinePacks, BUILTIN_PACK, fileCheckpointStore, jsonlAuditSink } from '@tramo/runtime';
import GITHUB from '@tramo/github';
import myFlow from './my-flow.json' assert { type: 'json' };

const { executors, nodes } = combinePacks([BUILTIN_PACK, GITHUB]);

const server = createTramoServer({
  workflows: { myFlow },
  executors,
  nodes,                                  // used to find secret fields for redaction
  checkpoints: fileCheckpointStore('./state'),
  audit: jsonlAuditSink('./audit.jsonl'),
  apiKey: process.env.TRAMO_API_KEY,      // optional bearer auth on /api
});

const port = await server.listen(3000);
console.log(`listening on ${port}`);

Quick start (CLI / Docker)

# CLI — built-in nodes only
npx tramo-server ./workflows --port 3000 --checkpoints ./state

# Docker
docker build -t tramo-server .
docker run -p 3000:3000 -v "$PWD/workflows:/workflows" -e TRAMO_API_KEY=secret tramo-server

Management API

| Method & path | Purpose | |---|---| | GET /api/health | liveness + counts | | GET /api/stats | dashboard aggregates (success rate, cost, tokens) | | GET /api/workflows | list loaded workflows | | GET /api/workflows/:id | one workflow doc | | POST /api/workflows/:id/run | trigger a run (body = trigger payload) | | GET /api/runs | recent runs (?limit&workflowId&status) | | GET /api/runs/:runId | one run record | | POST /api/runs/:runId/replay | re-run with the recorded trigger | | POST /api/runs/:runId/approve | resume a suspended run ({ approved, by?, key? }) | | GET /api/approvals | pending approvals |

Any path not under /api is dispatched to a matching webhook-trigger.

Approvals

A workflow that hits an approval-gate returns 202 (webhook) or status: "suspended" (API) with the pending requests. Resume it:

curl -X POST localhost:3000/api/runs/$RUN_ID/approve \
  -H "authorization: Bearer $TRAMO_API_KEY" \
  -d '{"approved": true, "by": "alice"}'

Suspended runs are persisted via the checkpoint store, so they survive a restart — load the run and approve it after the process comes back up.