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

godprotocol-cli

v0.1.3

Published

GodProtocol Node.js framework CLI

Downloads

41

Readme

godprotocol-cli

CLI for scaffolding GodProtocol Node.js framework projects.

Usage

mkdir my-api
cd my-api
npx godprotocol-cli init

This copies the GodProtocol project skeleton into the current directory:

my-api/
├── handlers/
│   └── v1/
├── routes/
│   ├── index.js
│   └── router-v1.js
├── services/
│   └── index.js
├── services.config.js
├── index.js
└── my-api.js

Then install the peer dependency and run it:

npm install express
node index.js

Development

Run the CLI locally without publishing:

node bin/godprotocol-cli.js init

Run tests:

npm test

Design

godprotocol-cli stays thin. It doesn't encode the framework's architecture itself — it just renders the skeleton in templates/project/ into the current working directory, substituting {{PROJECT_NAME}} for the target directory's name.

godprotocol-cli
        │
        │ init
        ▼
 templates/project/
        │
        ▼
 user's GodProtocol application

As the framework grows, the generated project can depend on a versioned GodProtocol runtime package, while this CLI stays responsible only for initialization.