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

git-prodman

v0.2.1

Published

Git-native product management. Local-first, AI-native, MIT licensed.

Readme


git-prodman is a CLI tool that brings product management into your Git repository. PRDs, specs, epics, decisions—all stored as version-controlled YAML and Markdown files. No SaaS, no accounts, no cloud sync. Just Git.

Why?

  • Context fragmentation kills products. Specs in Notion, tasks in Jira, decisions in Slack, code in GitHub. git-prodman puts everything in one place: your repo.
  • Git is the best database for versioned, collaborative documents. Every edit creates a commit. Every merge is a sync.
  • AI works better with context. When your product artifacts live alongside your code, AI assistants can understand the full picture.

Features

  • 📝 Specs & Epics — YAML + Markdown files with schema validation
  • 🚶 User Journeys — Map user experiences with steps, emotions, and touchpoints
  • 🗺️ Roadmap — Timeline view of milestones and releases
  • 🤖 AI Assistant — Query your product with natural language (OpenAI, Anthropic, Ollama)
  • 🌐 Bundled Web UI — Visual editor served locally, no separate install
  • 🔀 Git-Native — Every save is a commit, sync when ready
  • 🔍 Full-Text Search — Find anything across all artifacts
  • 🌙 Dark/Light Mode — Easy on the eyes

Installation

npm (recommended)

npm install -g git-prodman

From source

git clone https://github.com/git-prodman/git-prodman.git
cd git-prodman
npm install
npm run build
npm link

Standalone binary

Download from Releases:

| Platform | Download | |----------|----------| | macOS (Apple Silicon) | prodman-macos-arm64 | | macOS (Intel) | prodman-macos-x64 | | Linux (x64) | prodman-linux-x64 | | Windows (x64) | prodman-win-x64.exe |

Quick Start

# Initialize in your project
cd your-project
prodman init

# Create your first epic
prodman epic create

# Start the web UI
prodman ui

This creates a .prodman/ directory:

.prodman/
├── product.yaml      # Product vision & OKRs
├── roadmap.yaml      # Milestones & releases
├── config.yaml       # Project settings
├── epics/            # Epic YAML files
├── specs/            # Spec Markdown files
├── issues/           # Issue tracking
├── decisions/        # Architecture Decision Records
├── journeys/         # User Journey maps
└── templates/        # Templates for new artifacts

Commands

Core Commands

prodman init              # Initialize .prodman/ in current repo
prodman ui [--port 3333]  # Start web UI
prodman status            # Show project overview

Artifact Management

# Epics
prodman epic create       # Create new epic (interactive)
prodman epic list         # List all epics
prodman epic show EP-001  # Show epic details

# Specs
prodman spec create       # Create new spec
prodman spec list         # List all specs
prodman spec show SP-001  # Show spec details

# Issues
prodman issue create      # Create new issue
prodman issue list        # List all issues

# User Journeys
prodman journey create    # Create new user journey
prodman journey list      # List all journeys
prodman journey show UJ-001  # Show journey details
prodman journey update UJ-001 --add-step  # Add steps interactively

# Decisions (ADRs)
prodman decision create   # Create new ADR
prodman decision list     # List all decisions

Git Operations

prodman sync              # Push commits to remote
prodman pull              # Pull with conflict detection
prodman diff              # Show uncommitted changes
prodman conflicts         # List files with merge conflicts
prodman resolve <file>    # Resolve merge conflicts

Search & AI

prodman search "auth"              # Full-text search
prodman ask "What's our MVP scope?" # AI query
prodman "summarize the roadmap"    # Bare AI query

Configuration

prodman config show       # Show current config
prodman config set        # Interactive configuration
prodman config path       # Show config file location

Web UI

Start the bundled web interface:

prodman ui

Opens http://localhost:3333 with:

  • Dashboard — Project stats, Git status, recent activity
  • Roadmap — Timeline view of milestones
  • Epics — Table view with status badges
  • Specs — List + split-pane Markdown editor
  • Journeys — User journey maps with step visualization
  • Kanban — Drag-and-drop board for epics and issues
  • Files — Tree explorer for .prodman/ directory
  • AI — Chat interface with streaming responses

Screenshots

The dashboard shows project stats, Git status, and recent epics.

Browse and view all .prodman/ files in a tree structure.

AI Integration

git-prodman supports multiple AI providers:

OpenAI

prodman config set
# Select: openai
# Enter API key: sk-...
# Model: gpt-4o (default)

Anthropic (Claude)

prodman config set
# Select: anthropic  
# Enter API key: sk-ant-...
# Model: claude-3-5-sonnet-20241022 (default)

Ollama (Local)

# Start Ollama first
ollama serve

prodman config set
# Select: ollama
# Endpoint: http://localhost:11434 (default)
# Model: llama3.2 (default)

Usage

# CLI queries
prodman ask "What are our P0 epics?"
prodman "How should we approach the auth system?"

# Web UI
# Click the 🤖 AI tab and chat directly

Philosophy

Git is the Database

No external database. No sync service. Your Git repo IS the source of truth. This means:

  • Version history for free — Every change is a commit
  • Collaboration via Git — PRs, branches, merge conflicts
  • Backup = push — Your remote is your backup
  • Works offline — No internet required

Local-First

  • All data stays on your machine
  • No telemetry, no analytics, no tracking
  • No user accounts or authentication
  • Works in air-gapped environments

AI-Optional

  • Full functionality without AI
  • Bring your own API keys
  • Support for local models (Ollama)
  • Context stays private

MIT Licensed

  • 100% open source
  • Fork it, modify it, sell it
  • No "open core" upselling
  • Community-driven development

File Formats

Epic (YAML)

id: EP-001
title: "User Authentication"
status: in_progress  # planning | in_progress | complete | cancelled
priority: p0         # p0 | p1 | p2 | p3
owner: "@alice"
milestone: v1.0-mvp

description: |
  Implement secure user authentication with OAuth2 support.

acceptance_criteria:
  - "[ ] Login with email/password"
  - "[ ] OAuth2 (Google, GitHub)"
  - "[x] Password reset flow"

progress: 60

Spec (Markdown + Frontmatter)

---
id: SP-001
title: "Auth API Design"
status: draft  # draft | review | approved | implemented
epic: EP-001
author: "@bob"
---

# Auth API Design

## Overview

This spec describes the authentication API endpoints...

User Journey (Markdown + Frontmatter)

---
id: UJ-001
title: "First-time project setup"
persona: "open-source-maintainer"  # References target_users in product.yaml
goal: "Initialize prodman in an existing repository"
status: draft  # draft | validated | implemented | deprecated
priority: p1
steps:
  - order: 1
    action: "Install prodman via npm"
    touchpoint: cli  # cli | web-ui | docs | api | external
    emotion: neutral  # frustrated | confused | neutral | satisfied | delighted
    pain_points: []
    opportunities: []
  - order: 2
    action: "Run prodman init"
    touchpoint: cli
    emotion: satisfied
    pain_points: []
    opportunities:
      - "Could auto-detect project type"
epics:
  - EP-001
---

# First-time project setup

## Overview

This journey maps the experience of setting up prodman for the first time...

Development

# Clone
git clone https://github.com/git-prodman/git-prodman.git
cd git-prodman

# Install dependencies
npm install

# Run in development
npm run dev -- --help
npm run dev -- ui

# Build
npm run build

# Type check
npm run typecheck

# Build standalone binaries
npm run pkg

Contributing

Contributions welcome! Please read our contributing guidelines first.

  1. Fork the repo
  2. Create a feature branch (git checkout -b feat/amazing-feature)
  3. Commit changes (git commit -m 'Add amazing feature')
  4. Push to branch (git push origin feat/amazing-feature)
  5. Open a Pull Request

License

MIT — Use it however you want.