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

@gogd-core/ggd

v0.1.9

Published

GoGoodDev workspace CLI

Readme

@gogd-core/ggd

GoGoodDev workspace CLI — a unified command-line tool for environment management, git workflows, and Jenkins CI integration.

Install

npm install -g @gogd-core/ggd

Shell tab-completion is auto-installed on npm install -g (bash, zsh, powershell).

Requirements

  • Node.js 20+

Commands

ggd env — Environment Management

ggd env use <name>    # Switch to a named environment

ggd run — Execute Shell Commands

ggd run <command...>  # Run any shell command via cross-platform executor

ggd rsh — Git Reset Hard (Safe)

Reset current branch to origin/<branch> with safety checks.

ggd rsh

Shows current branch name and uncommitted change count before prompting for confirmation. Prevents accidental data loss.

ggd mt — Merge Tool

Merge current branch into a target branch with automatic branch management.

ggd mt <target-branch>

Switches to the target branch (re-creates from origin if it exists locally), then merges the source branch with confirmation.

ggd jenkins — Jenkins CI Integration

Trigger and monitor Jenkins builds from the terminal.

Setup

# Interactive setup (manual entry)
ggd jenkins setup

# Setup with a team preset file (recommended)
ggd jenkins setup --preset <path-to-preset.json>

Saves config to ~/.ggd/jenkins.json. Re-running setup preserves existing values.

Build

# List available build targets
ggd jenkins build

# Trigger a build with defaults
ggd jenkins build <target>

# Override parameters
ggd jenkins build <target> --KEY=value --KEY2=value2

# Trigger without watching (detached mode)
ggd jenkins build <target> --detach

The build command will:

  1. Trigger the Jenkins job via REST API (with CSRF crumb support)
  2. Poll the queue until the build starts
  3. Stream console output (last 5 lines) in real-time
  4. Send a desktop notification when done (Windows/macOS/Linux)

Use --help to see all targets with their default parameters:

ggd jenkins build --help

View Config

ggd jenkins config    # Print current config as JSON

ggd completion — Shell Completion

Tab-completion is auto-installed globally. To manually output the script:

ggd completion          # Auto-detect shell
ggd completion bash
ggd completion zsh
ggd completion powershell

Preset Files

Teams can share Jenkins configuration via preset files. These are JSON files that define environments, job paths, and build targets:

{
  "url": "http://jenkins.example.com",
  "environments": {
    "staging": {
      "ui": "staging/job/frontend",
      "api": "staging/job/api"
    },
    "production": {
      "ui": "production/job/frontend",
      "api": "production/job/api"
    }
  },
  "targets": [
    {
      "name": "ui",
      "displayName": "UI (Frontend)",
      "jobPathKey": "ui",
      "defaults": {
        "COMMIT_HASH": "a-staging",
        "SITE": "acc"
      }
    }
  ]
}

Load with: ggd jenkins setup --preset <file>

Configuration

All config is stored at ~/.ggd/jenkins.json. No environment variables required.

License

Private