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

@strantalis/workset

v0.2.1

Published

Go CLI for multi-repo workspaces with linked worktrees

Readme

Workset

test lint goreleaser release-please docs

Workset is a Go CLI for managing multi-repo workspaces with linked Git worktrees by default. It captures intent ("these repos move together") and keeps multi-repo work safe, explicit, and predictable.

Why Workset

  • Workspaces first: treat related repos as a single unit of work.
  • Linked worktrees by default: branch work happens in isolated directories without duplicating repos.
  • Explicit remotes: base vs write remotes are always deliberate.
  • Templates: reusable repo sets that expand into workspace config.
  • Safe defaults: no destructive actions without explicit flags.

Status

Workset is in active development. Current commands focus on workspace creation, repo add, status, and groups/templates. Branch/worktree workflows are next.

[!WARNING] This project is under active development; interfaces and behavior may change without notice.

Quickstart

Install (recommended):

brew tap strantalis/homebrew-tap
brew install workset

Alternative (Go install):

go install github.com/strantalis/workset/cmd/[email protected]

Create a workspace and add repos:

workset new demo
workset repo add [email protected]:your/org-repo.git -w demo
workset status -w demo

Templates:

./workset group create platform
./workset group add platform repo-alias
./workset group apply platform -w demo

Sessions (tmux/screen/exec):

./workset session start demo -- zsh
./workset session attach demo
./workset session show demo
./workset session stop demo

Concepts

  • Workspace: a directory with workset.yaml and .workset/ state.
  • Repo sources: local paths stay put; URL clones land in ~/.workset/repos (configurable).
  • Worktrees: worktrees live under <workspace>/<repo> by default.
  • Remotes: base (truth) and write (fork/origin).
  • Templates: global repo sets applied into a workspace.

Docs

Docs are built with MkDocs + Material. The site config is mkdocs.yml, markdown content lives in docs/, and the published site is workset.dev.

Local dev (requires uv):

make docs-serve

Roadmap

  • Branch create/checkout + worktree management
  • Fetch/pull/exec across repos
  • Scoped status and JSON output