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

@livqeno/server

v0.1.0

Published

Official server SDK for the Livqeno hosted platform — mint short-lived RTC tokens, manage rooms, and read connection/error diagnostics from your own backend. Never for use in a browser.

Readme

@livqeno/server

Livqeno's backend SDK — mint short-lived RTC and chat tokens, manage rooms and live streams, and read connection/error diagnostics.

Part of Livqeno, managed real-time communication infrastructure.

Never import this in a browser. It holds a permanent project API key. The browser gets a short-lived token that this SDK mints.

Install

npm install @livqeno/server

Use

Identity comes from your session — never from the request body, or any caller can claim to be anyone.

import { Swalvo } from '@livqeno/server';

const swalvo = new Swalvo({
  apiKey: process.env.SWALVO_API_KEY!,
  baseUrl: process.env.SWALVO_API_URL!, // https://api.livqeno.com
});

const grant = await swalvo.tokens.create({ room: roomId, identity: 'user-42' });
// grant = { token, endpoint, iceServers, telemetryUrl, expiresAt, ... }

Hand grant to your frontend, which passes it to @livqeno/rtc.

Tokens are subscribe-only by default. A participant who should send camera, microphone or data needs it granted explicitly, or the client's enableCamera() / enableMicrophone() fail with a publish-permission error:

await swalvo.tokens.create({
  room: roomId,
  identity: 'user-42',
  permissions: { publish: true, publishAudio: true, publishVideo: true },
});

Moderate a live call, change a participant's metadata, or send a data message from the server:

await swalvo.rooms.muteParticipant(roomId, 'alice', { kind: 'audio', muted: true });
await swalvo.rooms.updateParticipantPermissions(roomId, 'alice', { publish: false });
await swalvo.rooms.updateParticipant(roomId, 'alice', { attributes: { hand: 'raised' } });
await swalvo.rooms.sendData(roomId, 'meeting ends in 5 min', { topic: 'system' });
await swalvo.rooms.removeParticipant(roomId, 'alice');

Verify a webhook delivery (pass the raw body):

import { verifyWebhook } from '@livqeno/server';

// Pass the request headers: `swalvo-signature` is checked first, then the
// legacy `raven-signature` header (same value) as a fallback.
const event = verifyWebhook(rawBody, req.headers, process.env.SWALVO_WEBHOOK_SECRET!);

Errors

import { SwalvoError, isSwalvoError } from '@livqeno/server';

Every failure carries the API's error code and the HTTP statusCode (undefined only when the request never reached the API, e.g. a network error), so you branch on the cause rather than parse a message.

try {
  await swalvo.tokens.create({ room, identity });
} catch (e) {
  if (isSwalvoError(e) && e.statusCode === 401) { /* bad or revoked API key */ }
}

Error codes keep their original RAVEN_* prefix (for example RAVEN_AUTH_ERROR) — they are part of the stable wire contract, so match on them as-is. The full list is in the error reference.

Documentation

Python backend? See Livqeno's Python SDK. It is not on PyPI yet — it will publish as swalvo-sdk.

License

MIT