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

@dash-ota/backend

v0.5.1

Published

Config-driven, plug-and-play OTA distributor for React Native (dash-ota). Mounts into Express/Connect via one middleware or runs standalone. Serves pre-signed manifests + ciphertext; never holds the signing key.

Downloads

579

Readme

@dash-ota/backend

The server half of dash-ota, self-hosted over-the-air updates for React Native. It stores the releases @dash-ota/cli publishes and hands them to devices: it checks each device's request signature (ECDSA P-256 device keys), picks the release a device should get (runtime version, channel, rollout), issues download tokens and records adoption. It never signs anything and never holds your signing key, so a breach of this server can't produce an update your apps will accept.

Docs: https://scripting-bear.github.io/dash-ota/docs/backend/installation

Install

Node 20.19 or later.

npm install @dash-ota/backend
npm install express   # only if you mount it into Express

Use

// server.mjs
import express from 'express';
import { dashOtaMiddleware, rawBodySaver } from '@dash-ota/backend';

const app = express();

// Request signatures cover the raw body; release manifests can exceed express.json's 100 kB default.
app.use(express.json({ limit: '32mb', verify: rawBodySaver }));

app.use(
  dashOtaMiddleware({
    adminToken: process.env.OTA_ADMIN_TOKEN,         // protects /admin/*; no default
    storageDir: '/var/lib/dash-ota/storage',         // release files
    dataDir: '/var/lib/dash-ota/data',               // release and device metadata
    verifyEnrollToken: async (token) => checkSession(token), // your own session check
    logger: console,
  }),
);

app.listen(4455);

checkSession stands for your own function that returns true for a valid user session token. Mount the middleware at the root: the routes are absolute (/ota/v2/*, /admin/*, /health, /ready) and anything else falls through to next(). The same routes are available as createOtaBackend(options) (with .middleware and .listen()), as a standalone server (node node_modules/@dash-ota/backend/dist/server.js, configured by environment variables), and through Postgres, SQLite, Redis and S3 adapters.

Upgrading from 0.5.0

0.5.0 kept its data inside node_modules/@dash-ota/backend/ by default, which npm install deletes. From 0.5.1 the defaults are <working directory>/.dash-ota/storage and .dash-ota/data, and the server refuses to start with a data directory inside node_modules. If you relied on the old defaults, copy node_modules/@dash-ota/backend/storage and .data somewhere safe before upgrading, and point storageDir and dataDir at them.

Configuration

Every option has an environment variable and a default that fails closed: https://scripting-bear.github.io/dash-ota/docs/backend/configuration

License

MIT