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

@appstock/via

v0.1.11

Published

Developer environment convergence CLI.

Vulnerabilities

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

Links

Maintainers

appstockappstock

Keywords

Readme

via

Developer environment convergence CLI for Appstock-Tech.

via converges your machine toward the desired state declared in the private workspace repo: repos to clone, AWS profiles, tool versions, and shared Claude Code skills/MCP servers. Updating the team's environment is a PR to workspace — no release of this CLI is required for config changes.

Install

npm i -g @appstock/via
mkdir ~/dev && cd ~/dev      # any directory you like — this becomes your workspace root
via setup

Commands

  • via setup — one-time onboarding (installs prerequisites, authenticates GitHub/Claude Code/MCP/AWS, clones repos, runs a full sync). Safe to re-run any time — every step checks current state first and prompts only for what's actually missing.
    • via setup --github|--claude|--mcp [--server <name>]|--aws [--profile <name>] [--force] re-runs a single credential step.
  • via sync — idempotent convergence. Self-updates, pulls workspace, clones/updates repos, installs Claude Code plugins/MCP servers, ensures the shell env fragment's content lines and the AWS config marker block, and installs/upgrades declared tools. Never prompts.
  • via doctor — read-only drift report with the exact fix for anything out of sync.
  • via uninstall — removes exactly what via added (AWS config block, shell env lines, plugins, marketplace). Cloned repos and ~/.aws/credentials are left untouched.

Development

npm install
npm run dev -- <command>   # run from source via tsx
npm test
npm run typecheck
npm run lint
npm run build               # bundles to dist/cli.mjs

Architecture

All desired state and shared content (skills, MCP servers, shell env fragment) lives in the private workspace repo — this CLI contains only logic. See src/lib/ for the convergence primitives (marker-block editing, single-line content management, the tool installer engine) and src/commands/ for the four subcommands, which compose those primitives against workspace/manifest.json.

The CI workflow (.github/workflows/ci.yml) scans the published npm pack tarball for AWS account ids, access key patterns, tokens, and internal hostnames on every push — this package must never contain org-internal data, which belongs only in the private workspace repo.