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

@crafter/cli

v0.5.2

Published

Ship projects to the Crafter Station community directory.

Downloads

0

Readme

@crafter/cli

Create reviewable Crafter Station Ship drafts from a local project, then publish only after explicit confirmation.

Install

npm install --global @crafter/cli

The CLI requires Node.js 18 or newer. Bun is not required.

Usage

crafter login
crafter whoami
crafter handle <handle>
crafter onboard --file <json-file> --confirm
crafter ship
crafter publish <draft-id> --revision <updated-at> --confirm
crafter edit <ship-slug> --file <json-file> --revision <updated-at> --confirm
crafter update <ship-slug> --file <json-file> --confirm

crafter handle checks whether a Crafter handle is still available. crafter onboard --file creates or updates your Crafter profile from a JSON file with at least handle and displayName (run it without arguments to use the browser form instead):

{
  "handle": "ada",
  "displayName": "Ada Lovelace",
  "bio": "Building compilers for fun.",
  "githubUrl": "https://github.com/ada",
  "originLocation": { "city": "London", "country": "United Kingdom", "countryCode": "GB" },
  "basedLocation": { "city": "London", "country": "United Kingdom", "countryCode": "GB" }
}

AI coding agents can follow crafter.run/join/agent.md to walk a user through joining.

Run crafter login yourself in a local interactive terminal and keep it open until the browser confirms login. The CLI rejects non-interactive agent command runners because ending that process also ends the localhost OAuth callback server.

If login fails with invalid_client or "The requested OAuth 2.0 Client does not exist", update with npm install --global @crafter/cli@latest and try again. The public CLI always uses Crafter's production OAuth application; environment variables cannot redirect authentication.

Ship update files contain a public changelog entry:

{
  "title": "Version 1.1",
  "description": "Added team workspaces and improved onboarding."
}

Use crafter edit to change a published Ship's metadata. Get the current updatedAt revision from crafter ships, then provide any fields to change in the JSON file:

{
  "tagline": "A sharper description of the project",
  "links": [{ "type": "website", "url": "https://example.com" }]
}

crafter update remains the command for publishing changelog entries.

The CLI inspects only README.md, package.json, crafter.ship.json, and the Git origin by default. OAuth credentials are stored in the operating-system credential store.

See the public Ships directory at crafter.run/ships.