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

@sanjay5114/cdx

v1.0.6

Published

Lightning-fast extensible CLI for developer productivity with modular commands, AI integrations, and automation.

Downloads

38

Readme

CDX

CDX — a fast, focused command-line tool that helps developers and teams manage projects, tasks, and settings from the terminal.

Why CDX exists

  • Problem: Developers waste time switching tools and writing repetitive setup scripts.
  • Solution: CDX centralizes common project operations (create, configure, run tasks) with simple commands so you can spend time building, not managing.

Key benefits

  • Save time: Quick project scaffolding and repeatable commands.
  • Consistency: Standardize workflows across machines and teams.
  • Lightweight: Focused feature set that integrates with your existing stack.

Core features

  • Create new projects from templates: cdx create <name>
  • Configure project and user settings: cdx config set <key> <value>
  • Authentication helpers for secure workflows: cdx auth login / logout
  • Task runner for common routines: cdx run <task>
  • Scriptable and CI-friendly: works in scripts and automation pipelines

Install

  • From npm: npm install -g cdx
  • From local folder: npm install -g .

Quick start

  1. Create a project
    • cdx create my-app
  2. Set configuration
    • cdx config set editor vim
  3. Run a task
    • cdx run build
  4. Authenticate (uses secure storage or environment-driven flow)
    • cdx auth login

Examples

  • Create and bootstrap:
    • cdx create blog && cd blog && cdx run init
  • Save a setting:
    • cdx config set project.timeout 30

Configuration

  • Use cdx config get/set to manage settings.
  • Configured values can be sourced from environment variables or secure stores; avoid storing sensitive secrets in plaintext files.

Security & privacy

  • Do not commit passwords, API keys, or private tokens to version control.
  • Prefer environment variables, system keychains, or dedicated secret managers for credentials.
  • CDX is designed to avoid embedding sensitive provider-specific implementation details in the README or default configs.

Best practices

  • Add CDX commands to project README or contributor docs for consistent onboarding.
  • Use CI environment variables for automation rather than local secrets.
  • Create lightweight templates for teams to standardize projects.

Contribution

  • Found a bug or have a feature idea? Open an issue or submit a pull request.
  • Keep changes small and well-documented. Add tests for new behavior where possible.

License

  • See package.json for the license. Ensure you follow the license when redistributing.

Support & contact

  • Open an issue in the repository for help or feature requests.
  • Include command output and steps to reproduce when reporting bugs.

Thank you for using CDX — built to reduce repetitive work and help teams move faster.