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

@akshatowo/artifacts

v0.0.7

Published

CLI for publishing and managing Artifacts.

Readme

Artifacts CLI

Command-line tools for uploading, listing, and opening Artifacts.

Requirements

The npm package ships a Bun-targeted executable script. Install Bun before using the CLI:

curl -fsSL https://bun.sh/install | bash

Installation

Install the CLI globally with npm:

npm i -g @akshatowo/artifacts

Then verify the command is available:

artifacts --help

Authentication

Sign in with the device-code flow:

artifacts auth login

The CLI prints a verification URL and a one-time code. Open the URL, sign in, enter the code, and wait for the CLI to finish.

Check the current signed-in user:

artifacts auth whoami

Sign out:

artifacts auth logout

Authentication is stored locally in:

  • macOS/Linux: ~/.config/artifacts/auth.json
  • Windows: %APPDATA%\artifacts\auth.json

Upload An Artifact

Upload an HTML artifact:

artifacts upload ./path/to/artifact.html

On success, the CLI prints the public artifact URL.

If you omit the path, the CLI prompts for a file:

artifacts upload

List Artifacts

List artifacts owned by the signed-in user:

artifacts ls

The output includes the artifact ID, name, creation time, and update time.

Get An Artifact URL

Print the URL for an artifact by ID:

artifacts get <artifact-id>

Example:

artifacts get 0192f2c2-8f0e-7000-9c41-68aaf2f4fd21

Share An Artifact

Make an artifact public and print its share link:

artifacts share <artifact-id>

Example:

artifacts share 0192f2c2-8f0e-7000-9c41-68aaf2f4fd21

Anyone with the printed /s/<artifact-id> link can view the artifact.

Stop sharing an artifact:

artifacts unshare <artifact-id>

After unsharing, the public share link stops working.

Configuration

By default, production builds use:

https://artifacts.4kshat.dev

Override the API base URL with BASE_URL:

BASE_URL=http://localhost:3000 artifacts ls

The auth device client ID defaults to artifacts-cli. Override it with AUTH_CLIENT_ID:

AUTH_CLIENT_ID=my-client artifacts auth login

Development

Build the distributable CLI:

bun run build

Run type checking:

bun run check-types

Test the built binary locally:

./dist/index.js --help

Preview the npm package contents:

npm pack --dry-run

Publishing

Before publishing, build and type-check:

bun run build
bun run check-types

Publish from this package directory:

npm publish