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

@askenaz-dev/forge-cli

v0.1.5

Published

Forge developer CLI — install governed Forge skills into your agent (Claude Code, Copilot, Codex, Cursor, Gemini CLI, …).

Vulnerabilities

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

Links

Git

Maintainers

askenazaskenaz

Keywords

Readme

@askenaz-dev/forge-cli (npm distribution)

This directory builds and publishes the forge CLI to npm under the @askenaz-dev scope using the optionalDependencies-per-platform pattern (same approach used by esbuild, biome, swc).

Layout

  • bin/forge.js — committed JS shim shipped inside the @askenaz-dev/forge-cli parent package; resolves and execs the platform-specific binary.
  • publish.mjs — release-time orchestrator. Reads cli/forge/dist/ (produced by goreleaser), generates one prebuilt npm package per platform, then publishes the parent.

How it works

Installing @askenaz-dev/forge-cli lets npm/pnpm/yarn/bun pick the matching @askenaz-dev/forge-cli-<platform>-<arch> optional dependency (skipping the others). The parent's bin/forge.js then spawnSync's the binary from that sub-package.

@askenaz-dev/[email protected]
├─ optionalDependencies
│   ├─ @askenaz-dev/[email protected]
│   ├─ @askenaz-dev/[email protected]
│   ├─ @askenaz-dev/[email protected]
│   ├─ @askenaz-dev/[email protected]
│   └─ @askenaz-dev/[email protected]
└─ bin/forge.js  → resolves & execs the matching sub-package's binary

Release flow

  1. Tag the repo with vX.Y.Z.
  2. .github/workflows/cli-release.yml runs goreleaser → produces cli/forge/dist/, the GitHub release, and the Homebrew formula in askenaz-dev/homebrew-tap.
  3. The same workflow runs node cli/forge/npm/publish.mjs with VERSION=$GITHUB_REF_NAME to publish all 5 platform packages + the parent.

Local dry-run

cd cli/forge
goreleaser release --snapshot --clean
cd npm
VERSION=v0.0.0-dev DIST=../dist DRY_RUN=1 node publish.mjs

Secrets required in CI

| Secret | Purpose | |---|---| | NPM_TOKEN | Automation token for the npm account/org that owns the @askenaz-dev scope | | HOMEBREW_TAP_GITHUB_TOKEN | PAT with repo scope on askenaz-dev/homebrew-tap |