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

@veris.works/github-profile-ops

v0.1.0

Published

GitHub profile README generator powered by prompt-ops-maker principles

Downloads

78

Readme


One-line result

GitHub API data + profile ops spec → README.md

Quick start

# Interactive setup (recommended for first-timers)
npx --yes [email protected]/github-profile-ops github-profile-ops <username> --interactive

# Preview before writing
npx --yes [email protected]/github-profile-ops github-profile-ops <username> --dry-run

# Write directly
npx --yes [email protected]/github-profile-ops github-profile-ops <username>

No install required. No API key. Works with any public GitHub account.

What it produces

Generated README includes:

  • Animated typing header (capsule-render + readme-typing-svg)
  • Auto-detected repo table (description, language — meta repos filtered)
  • Stack badges from actual repo languages
  • Stats & streak cards (toggleable)
  • Contribution snake (optional)
  • Color theme of your choice

How it works

fetchGitHubProfile(<username>)
  ↓
buildProfileOpsSpec()     ← same structure as prompt-ops-maker
  scope · verification gates · output constraints
  ↓
generateReadme(spec, opts)
  ↓
README.md

--show-spec to inspect the generated ops spec:

npx ... github-profile-ops <username> --show-spec
{
  "scope": "Generate a GitHub profile README for <username>",
  "gates": ["no_unverified_claims", "no_marketing_hype", "result_first", "no_secret_echo"],
  "output": { "format": "github_flavored_markdown", "style": "verification-first" }
}

Interactive mode

npx ... github-profile-ops <username> --interactive

Asks 4 questions:

  1. Custom tagline (or use existing bio)
  2. Color theme — Ocean Blue / Forest Green / Sunset Purple / Minimal Gray
  3. Include Stats & Streak cards?
  4. Include Contribution snake?

After generating, prints a step-by-step guide to activate the profile README on GitHub.

Options

| Flag | Description | |------|-------------| | --interactive, -i | Guided setup with questions | | --dry-run | Preview to stdout, no file written | | --show-spec | Print the profile ops spec as JSON | | --output=FILE | Write to FILE (default: README.md) |

Security boundary

  • GitHub public API only. No authentication needed.
  • No external LLM calls. All processing is local.
  • File write: only the --output path. Default: README.md in current directory.
  • no_secret_echo gate: tokens and internal paths are excluded from output.

Part of the verisworks-ai pipeline

prompt-ops-maker (write) → vibecodecheck (audit) → MCP servers (serve)
        ↑
github-profile-ops — profile README, same ops-spec structure

Requirements

  • Node.js 18+
  • Internet connection (GitHub API)

License

MIT — verisworks-ai