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

duetfs

v0.1.0

Published

`duetfs` is the agent-facing CLI for Duet workspaces. It is a thin client over the Duet REST API: authentication, files, memory, and workspace provisioning all go through `ctl.duet.so/v1` or the configured test API. The CLI owns no server logic and does n

Readme

duetfs

duetfs is the agent-facing CLI for Duet workspaces. It is a thin client over the Duet REST API: authentication, files, memory, and workspace provisioning all go through ctl.duet.so/v1 or the configured test API. The CLI owns no server logic and does not shell the agent.

Configuration lives in ~/.duet/config.json with mode 0600. It stores the API key, the default workspace, and the API base URL. DUET_API_URL and --api-url override the stored base URL for tests and local runs. API keys are never printed.

Addresses use the contract-owned workspace:/path grammar. After duetfs workspace use <slug>, slash-prefixed paths such as /notes/today.md resolve through that default workspace.

Run duetfs --help for the command surface. duetfs --version reports the published artifact version. Every command supports stable --json output.

Sync (macOS)

duetfs sync mirrors every workspace you belong to into ~/duet/<workspace> and keeps both sides live over stock Syncthing (the one transfer engine — supervised, bridged, and orchestrated by this package; never forked). It is macOS-only in this release.

  • duetfs sync install / uninstall — a per-user launchd LaunchAgent that runs the daemon at login (keep-alive); symmetric and idempotent.
  • duetfs sync status [--json] — per-workspace state read from the daemon's snapshot: up to date / syncing / retired / conflicts.
  • duetfs sync run <workspace> [dir] — one workspace, foreground, to convergence (the slice-21 one-shot).
  • duetfs sync daemon — the long-running entrypoint launchd invokes; not run by hand.

The Syncthing binary is pinned and ships per-arch in exact-versioned @duetso/syncthing-<os>-<arch> optionalDependencies, sha256-verified on resolve. binary.ts is the single pin; bun run release:syncthing stages the binaries into those packages and dry-run-packs them. DUET_SYNCTHING_BIN overrides the resolver with a local binary for development. The full, first-time-user guide (install, git discipline, conflicts, retirement) lives in the docs "Sync to your Mac" page.

The daemon never exposes Syncthing's admin API (loopback only), and .git / node_modules never mirror — git history travels via real remotes.

Exit Codes

| Code | Meaning | | ---- | ---------------------------------------------------------------------------------- | | 0 | Success | | 3 | Authentication failed or no stored login | | 4 | Insufficient scope; JSON errors include the required scope when the API returns it | | 5 | Not found | | 6 | Network error | | 64 | Usage error |