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

@decentnetwork/beagle

v0.1.6

Published

Beagle — P2P chat, file transfer and calls for regular users, on the Decent Network. No admin privilege required.

Readme

Beagle

P2P chat, file transfer and calls over the Decent Network. No account, no server, no admin privilege — your identity is a keypair on your own machine, and messages go peer-to-peer.

Beagle is the application. The protocol lives in @decentnetwork/peer (SDK) and the virtual-LAN layer in @decentnetwork/lan (decentlan, a developer and operator tool). Beagle iterates fast; those stay boring on purpose.

Run

npm install
npm run build
node dist/cli.js

Then open http://localhost:8766.

--port <n>         HTTP port (default 8766)
--host <addr>      bind address (default 127.0.0.1)
--config-dir <p>   identity/config dir (default ~/.agentnet)
--dora-dir <p>     dora roster dir, if this machine runs a dora

Port 8766 rather than decentlan's 8765, so during the transition the old agentnet ui and Beagle can run side by side on one machine.

Calls (web ↔ Android)

Online WebRTC with the Android app uses Carrier bootstrap TURN, not the tokyo messaging relay. See docs/webrtc-android-interop.md for the failure modes and how the first-call cold-start was fixed.

Status: Phase 1

Beagle picks a backend for its Carrier identity. Exactly one is ever live, because one identity must never run two Carrier peers at once — two peers on the same keypair race on session establishment and corrupt each other's state.

| Backend | Status | Needs root | Virtual LAN | |---|---|---|---| | daemon — talks to a running decentlan daemon over IPC | shipping | no (the daemon does) | yes | | embedded — Beagle opens its own Peer in-process | Phase 2 | no | no |

Today Beagle requires a decentlan daemon. Phase 2 adds the embedded backend, at which point Beagle runs standalone at ordinary user privilege and decentlan becomes the optional "I also want a virtual LAN" add-on.

Identity is read from ~/.agentnet by default, so a machine already running decentlan keeps the same userid and the same friends — it is the same node, not a new one.

Layout

src/
├── cli.ts        # the `beagle` binary — argument parsing, startup
├── peer-host.ts  # backend abstraction + selection (the split's hinge)
├── ipc.ts        # decentlan daemon wire protocol, client side
├── server.ts     # local HTTP server: /api/* + serves the UI bundle
├── exits.ts      # official exit table (network panel only)
└── desktop/      # the UI itself (JSX, concatenated + esbuild-transpiled)

scripts/build-ui.mjs bundles src/desktop/*.jsx into dist/desktop/app.js. The UI runs as one concatenated script sharing global scope with React (UMD) — no CDN, no in-browser Babel.