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

@openducktor/web

v0.3.1

Published

Local browser runner for OpenDucktor.

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Git

Maintainers

maxsky5maxsky5

Keywords

Readme

@openducktor/web

Local browser runner for OpenDucktor.

bunx @openducktor/web

The CLI starts the OpenDucktor Rust web host on 127.0.0.1, waits for readiness, serves the bundled OpenDucktor frontend, and shuts the host down with a control-token-protected request when the process exits. The browser shell receives a launcher-generated app token, opens an HttpOnly host session cookie through /session, and fails fast if the launcher does not inject the local host URL or token.

Development

From the OpenDucktor repository root:

bun run browser:dev

That workspace mode runs the Rust host through Cargo and serves the frontend with Vite. Published installs use bundled static frontend assets plus packaged macOS host and MCP sidecar binaries with .sha256 checksum files. Missing or mismatched packaged artifacts fail startup before any fallback is attempted.

Options

bunx @openducktor/web --port 1420 --backend-port 14327
  • --port: frontend server port
  • --backend-port: local Rust host port
  • --host-binary: explicit host binary path for local testing

OpenDucktor is macOS-first; packaged web-host binaries currently support Apple Silicon and Intel macOS.

Release contents

The npm package must include:

  • bin/openducktor-web-host-darwin-arm64
  • bin/openducktor-web-host-darwin-arm64.sha256
  • bin/openducktor-mcp-darwin-arm64
  • bin/openducktor-mcp-darwin-arm64.sha256
  • bin/openducktor-web-host-darwin-x64
  • bin/openducktor-web-host-darwin-x64.sha256
  • bin/openducktor-mcp-darwin-x64
  • bin/openducktor-mcp-darwin-x64.sha256
  • dist/cli.js
  • dist/web-shell/**

The release workflow builds those binaries, verifies checksums and package contents, dry-runs npm packaging, and publishes the single self-contained @openducktor/web package.