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

@v3b/project-manager

v0.2.1

Published

A tool to manage your local projects.

Readme

@v3b/project-manager

A tool to manage your local projects.

🤖 Code of this project is generated via Cursor.

Features

  • Add projects: Clone GitHub repositories to organized local directories
  • Scan directories: Automatically discover and add existing Git repositories
  • List projects: View all managed projects in table or tree format
  • Navigate projects: Quickly jump to project directories using keywords

Commands

vpm add <repo>

Clone a GitHub repository to a corresponding local directory.

# Clone using HTTPS URL
vpm add https://github.com/owner/repo

# Clone using SSH URL
vpm add [email protected]:owner/repo.git

# Clone using alias format
vpm add gh:owner/repo

vpm scan <dir>

Scan a directory for Git repositories and add them to the project manager.

# Scan current directory
vpm scan .

# Scan with custom depth
vpm scan /path/to/directory --depth 3

# Dry run to see what would be added
vpm scan . --dry-run

vpm list

List all managed projects.

# List all projects
vpm list

# Filter by hostname
vpm list --host github.com

# Filter by directory
vpm list --dir /path/to/workspace

# Show in tree format
vpm list --format tree

vpm go <keyword>

Navigate to a project directory by searching for keywords in project names.

# Navigate to a specific project
vpm go my-repo

# When multiple projects match, you'll get an interactive selection
vpm go repo

Examples:

  • vpm go my-repo - Directly navigates to the my-repo project
  • vpm go repo - If multiple projects contain "repo" in their name, shows an interactive selection menu

The search is case-insensitive and matches against hostname, owner, and repository name.

Configuration

The project manager uses a TOML configuration file located at ~/.vpm.toml to customize its behavior. If no configuration file exists, default settings will be used.

Configuration File Structure

# Base directory for all projects (default: ~/workspace)
baseDir = "~/workspace"

# Host configurations
[host]
  # GitHub configuration
  [host.github]
    alias = "gh"
    hostname = "github.com"
    baseDir = "github"  # Optional: subdirectory under baseDir
    preferSSH = true    # Optional: prefer SSH over HTTPS

  # GitLab configuration
  [host.gitlab]
    alias = "gl"
    hostname = "gitlab.com"
    baseDir = "gitlab"
    preferSSH = true

  # Custom Git host configuration
  [host.custom]
    alias = "custom"
    hostname = "git.example.com"
    baseDir = "custom"
    preferSSH = false

Configuration Options

Global Options

  • baseDir (string): The base directory where all projects will be stored. Defaults to ~/workspace.

Host Configuration

Each host configuration supports the following options:

  • alias (string): Short alias for the host (e.g., gh for GitHub). Used in commands like vpm add gh:owner/repo.
  • hostname (string): The Git host's domain name (e.g., github.com).
  • baseDir (string, optional): Subdirectory under the global baseDir for this host's projects. If not specified, uses {baseDir}/{hostname}.
  • preferSSH (boolean, optional): Whether to prefer SSH URLs over HTTPS when cloning. Defaults to true for GitHub and GitLab.

Default Configuration

If no configuration file is found, the following defaults are used:

baseDir = "~/workspace"

[host.github]
alias = "gh"
hostname = "github.com"
preferSSH = true

[host.gitlab]
alias = "gl"
hostname = "gitlab.com"
preferSSH = true

Project Directory Structure

With the default configuration, projects are organized as follows:

~/workspace/
├── github.com/
│   ├── owner1/
│   │   ├── repo1/
│   │   └── repo2/
│   └── owner2/
│       └── repo3/
└── gitlab.com/
    └── owner3/
        └── repo4/

You can customize this structure by setting different baseDir values for each host in your configuration file.

Installation

npm install -g @v3b/project-manager

Development

# Install dependencies
pnpm install

# Build the project
pnpm run build

# Run tests
pnpm test

# Format code
pnpm run format

# Check code quality
pnpm run check