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

@eliware/cfhub

v15.1.0

Published

Cloudflare administration and automation CLI with GitHub CLI-style commands, profiles, safe writes, and direct API access.

Vulnerabilities

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

Links

Git

Maintainers

eli-sterlingeli-sterling

Keywords

cloudflarecliapi-clientoauthdnsworkersr2pagessecurityautomation

Readme

eliware.org

@eliware/cfhub npm License CI

Cloudflare administration and automation CLI with GitHub CLI-style commands, profiles, safe writes, and direct API access.

Table of Contents

Features

Use cfhub to manage Cloudflare resources, inspect account state, and call API endpoints. Use API-token or OAuth profiles. Preview supported writes with --dry-run and confirm destructive actions with --force.

Requirements

  • Install Node.js 26 or later.
  • Use a Cloudflare account and a scoped API token or OAuth access.
  • Set account or zone IDs when a command needs them.

Setup

Install the public package:

npm install --global @eliware/cfhub

Run cfhub auth login to save an API token. Run cfhub oauth login to use OAuth.

Usage

List zones and DNS records:

cfhub zones list
cfhub zones get --zone-id <zone_id>
cfhub dns-records list --zone-id <zone_id>

Preview a DNS write:

cfhub dns-records create --zone-id <zone_id> --data '{"type":"A","name":"www","content":"192.0.2.1"}' --dry-run

Read docs/README.md for user guides. Read specs/README.md for project specifications. Read RELEASE_NOTES.md for version history.

Development

Install dependencies before you run repository checks:

npm ci

Testing

Run aggregate checks from the repository root:

npm test

Run npm run test:e2e:web for OAuth browser checks. Read Web preview for browser setup, ports, and output files.

Troubleshooting

Read Setup and first use when login fails. Check that the token has the required Cloudflare permissions when a request fails.

Security

Keep API tokens, OAuth credentials, and local configuration files private. cfhub uses the operating system keychain when available.

Configuration

Read Profiles and settings for environment values, profiles, and storage paths.

Operations

Run cfhub auth status to view login status. Read Profiles and settings to control daily update checks.

Commands

Run cfhub --help to list commands. Run cfhub <resource> --help for actions. Read the command reference for command groups and global options.

Exit codes

cfhub returns 0 after success. It returns 1 after a command or API error. After SIGINT, cfhub exits with code 130. After SIGTERM, it exits with code 143.

Routes

The local OAuth server owns these routes when the scope picker is enabled:

  • GET / returns the scope picker.
  • POST /oauth/start accepts the selected scopes and redirects to Cloudflare.
  • GET /api/version?project=cfhub returns the package version.
  • GET /oauth-picker.css, /oauth-result.css, /oauth-picker.mjs, and /oauth-picker-app.mjs return picker files.
  • GET /picker/*.mjs, /escape-picker-markup.mjs, and /collect-picker-scope-boxes.mjs return picker modules.
  • GET /oauth-web/cf-logo.svg, /oauth-web/cloudflare-115x53.png, and /oauth-web/eliware-58x58.png return picker images.
  • GET /oauth/callback receives the OAuth callback.

Assets

The picker uses bundled files from src/oauth-web/ and these images from public/oauth-web/: cf-logo.svg, cloudflare-115x53.png, and eliware-58x58.png.

Development server

Run npm run start:web to start the OAuth picker preview on 127.0.0.1:1120. Read Web preview for browser workflows.

Build

Run npm run build after OAuth page or style changes. Webpack writes bundles to dist/.

Deployment

cfhub runs as a local CLI. The OAuth server runs on your computer during login.

Support

For help, questions, or to chat with the author and community, visit:

Discordeliware.org

eliware.org on Discord

Links

License

MIT © Eliware