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 🙏

© 2025 – Pkg Stats / Ryan Hefner

gittomd

v1.2.2

Published

Your entire GitHub repo, intelligently packaged into a single Markdown file via CLI.

Readme

gittomd CLI vs. Web

This is the official command-line interface (CLI) for gittomd. It brings all the powerful features of our web version directly to your terminal, allowing for local processing, scripting, and integration into your development workflow.

| Feature | gittomd CLI (This project) | gittomd.com | | --------------------- | :----------------------------: | :------------------------------------: | | Terminal Access | ✅ | ❌ | | Scripting/CI/CD | ✅ | ❌ | | Local Processing | ✅ | ❌ | | No Rate Limits | ✅ | ⚠️ | | Instant Access | ❌ | ✅ | | No Installation | ❌ | ✅ | | Caching | ❌ | ✅ |

Choose the CLI for power-user features and automation. Choose the web version for quick, one-off conversions without any setup.


✨ Key Features

  • ⚡ Blazing Fast: Optimized for performance with asynchronous file processing. Handles large repositories with ease.
  • 🧠 LLM-Optimized Formatting: Outputs clean Markdown with language-annotated code blocks (e.g., ## path/to/file.tsx``), a format that models like GPT-4 and Claude understand perfectly.
  • 🗑️ Intelligent Filtering: Automatically ignores binary files and common clutter (.git, node_modules, dist/, package-lock.json, etc.) to keep the context clean and focused.
  • 🌲 Clear Structure: Includes a file tree at the beginning of the Markdown file, giving a clear overview of the repository structure.
  • 💻 Purely Local: Clones the repository to a temporary local directory. No reliance on GitHub API rate limits for fetching file content.

📦 Installation

To use the gittomd CLI, you need to have Node.js (v18 or newer) and Git installed on your system.

Install gittomd globally using npm:

npm install -g gittomd

🛠️ How to Use

The basic command structure is:

gittomd <repository> [options]

Examples

1. Print Markdown to the console:

This will fetch the expressjs/express repository and print the combined Markdown directly to your terminal.

gittomd expressjs/express

2. Save Markdown to a file:

Use the -o or --output flag to specify a file path.

gittomd OpenSpace-Dev/gittomd-cli -o gittomd_project.md

This will create a file named gittomd_project.md in your current directory.

You can use full GitHub URLs as well:

gittomd https://github.com/vercel/next.js -o nextjs.md

Options

| Option | Alias | Description | Default | | ------------------ | ----- | -------------------------------------------------- | --------- | | --output <path> | -o | Output file path. | stdout | | --profile | | Show performance metrics after execution. | false | | --help | -h | Show help information. | |


🚀 Performance Benchmarks

gittomd is designed to be fast. The main bottleneck is cloning the repository, which depends on your network speed. The file processing itself is highly optimized.

Here are some benchmarks run on a standard machine (Apple M1, 16GB RAM) to demonstrate the processing speed after the repository is cloned:

| Repository | Total Files (approx.) | Time to Clone | Time to Process Files | | ----------------- | --------------------- | ------------- | ------------------------- | | expressjs/express | ~100 | ~16s | ~70ms | | facebook/react | ~2,500 | ~6s | ~890ms | | vercel/next.js | ~15,000+ | ~28s | ~2.6s |


🤝 Contributing

We welcome contributions of all kinds! Whether it's reporting a bug, suggesting a feature, or submitting a pull request, your help is appreciated.

Running the CLI Locally

  1. Clone the repository:

    git clone https://github.com/OpenSpace-Dev/gittomd-cli.git
    cd gittomd
  2. Install Dependencies & Build:

    npm install
    npm run build
  3. Link for local development: Use npm link to make the gittomd command available globally, pointing to your local code.

    npm link

    Now you can run gittomd from any directory.


❤️ Show Your Support

If you find gittomd useful, please give the repository a ⭐️ on GitHub! It helps the project gain visibility and encourages further development.