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

@eloquence98/ctx

v0.4.1

Published

Generate a truthful structural map of your codebase for AI and humans.

Readme

ctx

Dump a truthful structural index of a codebase.

No analysis. No opinions. No guessing.

ctx scans a directory and prints a map of folders, files, and trivially detectable exported symbols. It tells you exactly what exists — nothing more, nothing less.

Quick Start

No installation required. Run it directly with npx:

npx @eloquence98/ctx ./path-to-project

What It Does

ctx provides a high-level map of a project. It identifies:

  • Folders
  • Files
  • Exported symbols (both ES modules and CommonJS, when trivially detectable)

Exports that cannot be statically determined from source text are silently ignored.

Example Output

src/
├─ app.tsx → App
├─ utils.ts → formatDate, parseCurrency
└─ components/
   ├─ button.tsx → Button
   ├─ modal.tsx → Modal, ModalProps
   └─ styles.css

Files whose exports cannot be determined are listed without symbols.

Supported Export Patterns

ES Modules:

export function, export const/let/var, export class, export type, export interface, export default function/class

CommonJS:

exports.name = ..., module.exports.name = ..., module.exports = { name1, name2 }, module.exports = function/class

Why This Exists

When working with LLMs, new contributors, or legacy codebases, you don't always need the content of the files immediately, you need to understand the topology of the project first.

ctx gives you that map.

  1. Copy the output.
  2. Paste it into an LLM context window.
  3. Ask informed questions about the architecture before dumping raw code.

What It Does Not Do

ctx is intentionally shallow. That is why it is reliable.

  • Does not interpret architecture or infer domains
  • Does not explain code intent
  • Does not refactor or execute code
  • Does not read node_modules, .git, or environment files
  • Does not parse re-exports, barrel files, or computed names

See LIMITATIONS.md for detailed edge cases.

Configuration

No configuration required.

ctx automatically ignores:

  • node_modules, .git
  • Build outputs (dist, build, .next)
  • Environment files (.env)
  • Test files (.test., .spec.)
  • Hidden files and directories

Only .ts, .tsx, .js, .jsx files are scanned. Both ES module and CommonJS exports are detected.

Install (optional)

npm install -g @eloquence98/ctx
ctx ./src

Philosophy

Don't explain the code. Show the codebase as it exists.

ctx prefers truthful omission over incorrect inference. If something cannot be determined reliably, it is excluded.

License

MIT