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

@tuxx/orbit-embed

v0.1.9

Published

Embed Orbit surfaces — feedback, task board — inside any client app. Auth-bridged via HMAC-signed JWTs issued by the host backend.

Readme

@tuxx/orbit-embed

Drop Orbit Bridge surfaces (client chat and task board) directly inside a client's own app. Authentication is bridged via a short-lived HMAC-signed JWT issued by the client's backend — no Orbit accounts are created, no data leaves the client's user funnel.

v0.1 surface area

  • <OrbitProvider> — single client + token refresher
  • <OrbitClientPanel> — floating or inline client surface with messages, build status, files, and requests
  • <OrbitFeedback> — client dashboard chat composer + thread
  • <OrbitTaskBoard> — read-only client-safe task board for the active project

Install

npm install @tuxx/orbit-embed

Peer dependencies: react >= 18 and react-dom >= 18.

Ship the bundled stylesheet once per host app:

import "@tuxx/orbit-embed/styles.css";

Wire it up

Every new install should call the orbit-bridge Supabase Edge Function. The host app's backend must mint a short-lived HS256 JWT signed with the tenant's signing_secret (provisioned in Orbit admin → Bridge Settings).

Required claims:

| Claim | Meaning | | ------------ | ----------------------------------------------- | | tenant_id | embed_tenants.id issued during provisioning | | sub | Stable external user id in the client's app | | exp | Unix seconds; keep it short (≤ 15 minutes) | | email | Optional — surfaces in Orbit inbox | | name | Optional — surfaces in Orbit inbox |

Then, in the host React tree:

import {
  OrbitProvider,
  OrbitClientPanel,
} from "@tuxx/orbit-embed";
import "@tuxx/orbit-embed/styles.css";

export function ClientDashboardLayout() {
  return (
    <OrbitProvider
      endpoint="https://<project>.supabase.co/functions/v1/orbit-bridge"
      anonKey={import.meta.env.VITE_ORBIT_ANON_KEY}
      token={async () => {
        const res = await fetch("/api/orbit-bridge-token", {
          credentials: "include",
        });
        if (!res.ok) throw new Error(`Orbit token failed (${res.status})`);
        const data = await res.json() as { token: string };
        return data.token;
      }}
      theme="inherit"
    >
      <OrbitClientPanel mode="floating" launcherLabel="Support" />
    </OrbitProvider>
  );
}

Mount this from an authenticated dashboard/app layout only. Do not mount it in the public marketing site.

The token prop accepts either a string or an async function. Use the function form so the widget can fetch a fresh JWT as the old one nears expiry.

Server-side token minting (Node example)

import jwt from "jsonwebtoken";

export function mintOrbitJwt(user: { id: string; email?: string; name?: string }) {
  return jwt.sign(
    {
      tenant_id: process.env.ORBIT_TENANT_ID!,
      sub: user.id,
      email: user.email,
      name: user.name,
    },
    process.env.ORBIT_SIGNING_SECRET!, // base64 from Admin -> Bridge
    { algorithm: "HS256", expiresIn: "10m" },
  );
}

Token endpoints should return JSON:

{ "token": "<short-lived-orbit-tenant-jwt>" }

Rotate the signing secret at any time from Orbit Admin -> Bridge Settings. Old JWTs stop verifying the moment the rotation lands.

Allowed origins

Every tenant declares which origins are allowed to call the gateway. The edge function rejects any request whose Origin header isn't in the allowlist. Add http://localhost:5173 (or whatever your dev port is) to test locally.

What gets written to Orbit

  • Messages from <OrbitFeedback> land in public.inbox_messages with channel_type = 'orbit_bridge' and a reference back to the embed contact that sent them.
  • Structured bridge events are written to public.bridge_events.
  • Bridge commands are queued in public.bridge_commands for backend or browser listeners to poll and acknowledge.
  • Client requests and approvals are written to public.bridge_client_requests and mirrored into the Orbit inbox as orbit_bridge messages.
  • Client-visible tasks are read-only in v0.1 — the widget reads the tenant's active project via public.project_tasks and surfaces the client-safe projection.

What's next

  • <OrionChat> — conversational agent scoped to the tenant's Orbit data
  • Write mutations on the task board (status transitions, comments)
  • Guided repo installer that opens PRs against selected client dashboards