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

@ctroenv/cli

v1.3.0

Published

CLI tooling for CtroEnv — validate, generate, check, and document environment variables

Readme

@ctroenv/cli

npm version npm downloads license

CLI tooling for CtroEnv — validate, generate, check, document, and scaffold environment variables.

Installation

npm install @ctroenv/cli

Or use directly with npx:

npx @ctroenv/cli validate

Commands

| Command | Description | |---------|-------------| | validate | Validate environment variables against your schema | | generate | Generate .env.example from your schema | | check | CI-friendly diff of .env vs schema (exit code 1 on issues) | | docs | Generate Markdown or JSON documentation from your schema | | init | Scaffold a ctroenv.config file |

validate

Validate current environment against schema.

ctroenv validate [--source <path>] [--watch] [--json]

| Flag | Default | Description | |------|---------|-------------| | --source <path> | Config sources.default or process.env | Path to .env file | | --watch | false | Watch files and re-validate on change | | --json | false | Output JSON instead of formatted text |

generate

Generate .env.example from schema.

ctroenv generate [--output <path>] [--no-comments]

| Flag | Default | Description | |------|---------|-------------| | --output <path> | ".env.example" | Output file path | | --no-comments | false | Minimal output without comments |

check

CI-friendly diff of .env vs schema.

ctroenv check [--source <path>] [--strict] [--warn-unknown] [--json]

| Flag | Default | Description | |------|---------|-------------| | --source <path> | Config sources.default or ".env" | Path to .env file | | --strict | false | Also validate values against schema | | --warn-unknown | false | Warn about keys in source not in schema (with "did you mean?" suggestions) | | --json | false | Output JSON instead of formatted text |

Exit code 0 on success, 1 on missing/unused keys or validation errors.

docs

Generate documentation from schema.

ctroenv docs [--output <path>] [--format <format>]

| Flag | Default | Description | |------|---------|-------------| | --output <path> | "ENVIRONMENT.md" | Output file path | | --format <format> | "markdown" | Output format: markdown or json |

init

Scaffold a configuration file.

ctroenv init [--ts | --js | --json] [--minimal] [--from-env <path>]

| Flag | Default | Description | |------|---------|-------------| | --ts | Default format | Generate TypeScript config | | --js | — | Generate JavaScript config | | --json | — | Generate JSON config | | --minimal | false | Generate minimal config (schema path only) | | --from-env <path> | — | Generate schema stub from existing .env file |

Configuration

Create ctroenv.config.ts in your project root:

import { defineConfig } from "@ctroenv/cli"

export default defineConfig({
  schema: "./src/env.ts",
  sources: {
    default: ".env",
    production: ".production.env",
  },
  output: {
    example: ".env.example",
    docs: "ENVIRONMENT.md",
  },
  secrets: {
    mask: ["EXTRA_KEY"],
    maskWith: "***",
  },
})

Config Options

| Option | Type | Default | Description | |--------|------|---------|-------------| | schema | string | "src/env.ts" | Path to schema file | | sources.default | string | ".env" | Default env file path | | sources.production | string | — | Production env file path | | output.example | string | ".env.example" | Output path for generate | | output.docs | string | "ENVIRONMENT.md" | Output path for docs | | secrets.mask | string[] | [] | Additional keys to mask | | secrets.maskWith | string | "***" | Mask string override |

Types:

import { defineConfig } from "@ctroenv/cli"
import type { CliConfig, Format, ResolvedConfig } from "@ctroenv/cli"

const config: CliConfig = defineConfig({ schema: "./env.ts" })

Documentation

Full documentation at ctroenv.vercel.app

License

MIT