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

dotenv-linter-cli

v1.0.0

Published

Lint .env files for common issues: duplicate keys, empty values, spaces around =, invalid key names, and more

Readme

dotenv-linter-cli

Lint .env files for common mistakes — zero dependencies, pure Node.js.

npm license

Install

npm install -g dotenv-linter-cli

Or run without installing:

npx dotenv-linter-cli

Usage

dotenv-lint [options] [file...]

By default lints .env in the current directory.

dotenv-lint                        # lint .env
dotenv-lint .env.production        # lint a specific file
dotenv-lint .env .env.local        # lint multiple files
dotenv-lint --fix .env             # auto-fix fixable issues
dotenv-lint --strict .env          # enforce uppercase keys + quote consistency
dotenv-lint --json .env            # JSON output (for CI / tooling)

Rules

| Rule | Severity | Description | |------|----------|-------------| | DUPLICATE_KEY | ERROR | Same key defined more than once | | SPACES_AROUND_EQ | ERROR | KEY = value instead of KEY=value | | MISSING_EQ | ERROR | Line has a key-like word but no = sign | | EMPTY_VALUE | WARNING | KEY= with nothing after the equals sign | | INVALID_CASE | WARNING | Key contains lowercase letters | | MIXED_QUOTES | WARNING | Inconsistent quote style across values (--strict only) |

Example output

Linting: .env (12 lines)

  Line    3  ERROR    DUPLICATE_KEY    KEY "DATABASE_URL" defined twice (first at line 1)
  Line    7  WARNING  EMPTY_VALUE      KEY "SECRET_KEY" has empty value
  Line    9  WARNING  INVALID_CASE     KEY "api_key" should be uppercase: API_KEY
  Line   11  ERROR    SPACES_AROUND_EQ Use KEY=value, not KEY = value

4 issues (2 errors, 2 warnings)

Flags

| Flag | Description | |------|-------------| | --fix | Auto-fix: remove spaces around =, deduplicate keys (keeps last definition) | | --strict | Also enforce UPPERCASE keys and consistent quote style | | --json | Output a JSON array of { file, line, key, rule, severity, message } | | --help / -h | Show help | | --version / -v | Show version |

Exit codes

| Code | Meaning | |------|---------| | 0 | No issues | | 1 | Warnings only | | 2 | At least one error |

CI integration

# GitHub Actions example
- name: Lint .env files
  run: npx dotenv-linter-cli --json .env | tee lint-results.json

License

MIT