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

@aicdragon/geo-copilot

v0.1.0

Published

Chrome/Edge extension for GEO workflow: capture LLM answers, analyze platform patterns, generate publish-ready articles — all local-first.

Readme

GEO Copilot preview

Why GEO Copilot

GEO Copilot is built around a practical GEO loop:

  1. Search a product-related question in a general LLM.
  2. Capture the answer, recommended products, and cited source links.
  3. Open the cited platforms and learn the article structure.
  4. Rewrite a publish-ready article for the matched platform.
  5. Publish it, wait a few days, and test the same question again.
  6. Use the review result to plan the next optimization round.

Preview

The full workflow is focused on one repeatable loop: ask, capture, rewrite, publish, and review.

Features

  • Capture LLM answers and source links from platforms such as DeepSeek, Qwen, Doubao, Kimi, ChatGPT, and Claude.
  • Detect recommended product models, source domains, platform signals, answer structure, and content gaps.
  • Capture article structures from ordinary websites, forums, blogs, industry platforms, and official pages.
  • Separate LLM platforms from content platforms to avoid mixed analysis.
  • Generate GEO diagnosis, platform priority, article structure, publish-ready drafts, and post-publish review conclusions.
  • Rewrite reference content by borrowing structure while changing title angle, paragraph order, cases, FAQ, and parameter table.
  • Store data locally in chrome.storage.local by default.
  • Start analysis manually with GEO START, so each page is analyzed only when you choose.

Dashboard

| Section | Purpose | | --- | --- | | AI Diagnosis | Analyze model source patterns, platform priority, content gaps, and recommended article structure. | | GEO Rewrite | Turn reference structure and current product information into a publish-ready article. | | Post-publish Review | Compare new LLM answers after publishing and plan the next optimization round. | | Settings | Store long-term basics such as company/brand, industry scenario, banned claims, and API settings. | | Records | Keep diagnosis reports, drafts, review notes, and captured data separately. |

API Providers

The dashboard supports OpenAI-compatible /chat/completions APIs. Built-in presets include:

  • DeepSeek
  • Qwen
  • Doubao / Volcengine Ark
  • Kimi / Moonshot
  • Zhipu GLM
  • OpenAI
  • Custom OpenAI-compatible endpoint

API keys are stored only in local browser extension storage.

Install Locally

  1. Open Chrome or Edge extension management.
  2. Enable developer mode.
  3. Choose Load unpacked.
  4. Select this project folder.
  5. Pin GEO Copilot to the toolbar.

Package for Store Submission

Create a ZIP package with the extension files at the root:

Compress-Archive -Path manifest.json,popup.html,dashboard.html,src,assets,README.md,PRIVACY.md,STORE_LISTING.md -DestinationPath geo-copilot-v0.1.0.zip -Force

Do not include .git, demo, node_modules, or existing .zip files in the store package.

Repository Structure

manifest.json
popup.html
dashboard.html
src/
assets/
docs/images/
demo/
README.md
PRIVACY.md
STORE_LISTING.md

Privacy

GEO Copilot does not run a backend service. Captured page data, diagnosis reports, generated drafts, and API settings are stored locally in the browser unless you explicitly export or copy them.

When you use an external model API, prompt content is sent directly from your browser to the API endpoint you configure.

See PRIVACY.md for details.

Status

This is an MVP for validating a practical GEO workflow. Before public store release, review permissions, privacy text, screenshots, support links, and store listing copy.