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 🙏

© 2025 – Pkg Stats / Ryan Hefner

@mainframe/cli

v0.2.0

Published

Mainframe CLI

Downloads

3

Readme

Mainframe CLI

Usage

# In packages/cli
./bin/run

Commands

  • env:create: create a new environment
  • env:default: get or set the default environment to use
  • env:delete: delete an environment
  • env:list: list the environments
  • daemon:setup: configure the daemon binary and socket paths
  • daemon:status: display the daemon running status and socket path
  • daemon:start: start the daemon using the store configuration
  • daemon:stop: start the daemon using the store configuration
  • client:repl: open a node REPL with an injected client object connected to the daemon
  • client:setup: ensure the environment has a default vault setup
  • vault:create: create a vault
  • vault:delete: delete a vault
  • vault:list: list existing vaults
  • vault:settings: set and/or display a vault settings
  • graphql:query: execute a GraphQL query
  • graphql:schema: write the GraphQL schema
  • graphql:server: create a HTTP proxy for GraphQL queries
  • identity:create: create an identity
  • identity:list: list identities
  • app:create: create an app
  • app:publish: publish the app to Swarm
  • wallet:createEth: create a new Ethereum wallet
  • wallet:connectLedgerAccount: connect an account from ledger hardware wallet
  • wallet:delete: delete a wallet
  • wallet:importEth: import an Ethereum wallet

Environment setup

  1. Run env:create to create a new environment, set it as default unless you want to provide it explicitly in the next commands
  2. Run daemon:setup to configure the path to the daemon CLI, ex ./bin/run daemon:setup --bin-path=../daemon/bin/run
  3. Run daemon:start to start the daemon, use DEBUG="mainframe:*" ./bin/run daemon:start to see the logs
  4. Run client:setup to create a new vault and configure it to be used by default
  5. Run client:repl to start interacting with the daemon