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

envanalyzer-core

v0.1.0

Published

AST-based JS/TS environment variable analyzer with cross-file data flow tracing, confidence scoring, and family grouping

Readme

envanalyzer-core

AST-based JS/TS environment variable analyzer. Parses every process.env access pattern, traces dynamic keys across file boundaries, and returns a confidence-weighted usage map.

Install

npm install envanalyzer-core

Usage

import { analyze, loadConfig, generateEnvExample, FileAnalysisCache } from 'envanalyzer-core'

const config = await loadConfig('.')       // reads envanalyzer.config.js if present
const cache  = new FileAnalysisCache()     // optional — skip unchanged files

const result = await analyze({
  rootDir: '.',
  envTokens:        config.envTokens,       // optional custom family tokens
  envFamilyPrefixes: config.envFamilyPrefixes, // optional explicit family prefixes
  framework: 'vite',                        // optional — also detect import.meta.env
  cache,
})

console.log(result.missing)   // referenced in code, absent from .env
console.log(result.unused)    // declared in .env, never referenced
console.log(result.dynamic)   // dynamic accesses with trace results
console.log(result.families)  // environment-variant key groups

const example = generateEnvExample(result) // .env.example content

What it detects

| Pattern | Example | |---|---| | Static dot | process.env.DB_URL | | Static bracket | process.env["DB_URL"] | | Destructuring | const { DB_URL } = process.env | | Dynamic — local literal | const k = "DB_URL"; process.env[k] | | Dynamic — function return | const k = getKey(); process.env[k] | | Dynamic — cross-file import | import { KEY } from "./keys"; process.env[KEY] | | Template literal | process.env[`${svc}_API_KEY`] | | Vite | import.meta.env.VITE_KEY (with framework: "vite") |

Full documentation at the project repository.