Sjh9714
Audit your installed GitHub CLI extensions
Last verified:
What is Sjh9714?
The gh-extension-atlas audit tool is a browser-only page that helps developers audit their installed GitHub CLI extensions before installing more. Users run gh extension list in their terminal, paste the output into the page, and the audit runs entirely locally in the browser. The tool compares installed GitHub CLI extensions against the GitHub CLI Extension Atlas catalog to identify reviewed installs, unlisted tools, missing Top Picks, and workflow coverage gaps.
Key features include showing installed extensions that are already reviewed in the atlas, identifying installed extensions not listed yet, highlighting missing Top Picks, detecting workflow coverage gaps, and providing copyable install commands for missing workflow recommendations. The tool has no sign-in requirement, no analytics scripts, no remote audit API, and the pasted extension list is never uploaded anywhere.
This tool is for GitHub CLI users who want to make smarter extension install decisions, developers who want to audit their CLI tooling like they would audit dependencies, and anyone surprised by how many extensions they have without understanding workflow coverage. The goal is not to install every recommended extension but to make the next install decision smaller and easier to review.
The underlying catalog is available as JSON at https://sjh9714.github.io/gh-extension-atlas/api/extensions.json, with each entry including repository, category, install command, best-fit use case, avoid-if note, license, archived status, maintenance status, and verification date. This makes it usable by scripts, documentation tools, or coding agents that need current extension metadata.
Sjh9714 pricing
Pricing model: Freemium
Free tier - the audit tool is completely free with no paid plans. It is a static browser page with no sign-in, no analytics, and no remote API. The catalog JSON at https://sjh9714.github.io/gh-extension-atlas/api/extensions.json is also freely accessible. There are no subscription fees, no premium features, and no paid tiers mentioned.
Sjh9714 pros
- Runs entirely locally in browser with no data upload
- No sign-in required to use the tool
- No analytics scripts tracking usage
- No remote audit API calling external services
- Pasted extension list stays in browser only
- Provides copyable install commands for recommendations
- Identifies missing Top Picks in user's setup
- Detects workflow coverage gaps automatically
- Shows which extensions are already reviewed in atlas
- Highlights installed extensions not listed in catalog
- Static page that works without server dependencies
- Sample audit pre-loaded for immediate testing
- Helps avoid installing overlapping/redundant tools
- Covers maintenance status for each extension
- Includes avoid-if notes for better decision making
- JSON API available for scripts and documentation tools
- Conservative catalog approach prioritizes quality over quantity
Sjh9714 cons
- Only works with browser, no CLI interface
- Requires manually running gh extension list first
- Manual paste step instead of automatic detection
- Catalog may not include every existing extension
- No endorsement or code audit of extensions themselves
- Maintenance labels may not be real-time updated
- No mobile app or native desktop version
- Requires GitHub CLI already installed
- Sample data may not reflect user's actual setup
- No collaborative features for team audits
Frequently asked questions about Sjh9714
How do I use the audit tool?
Run gh extension list in your terminal, copy the output, paste it into the text box on the audit page, and review the results. The audit runs locally in your browser and shows reviewed installs, unlisted tools, missing Top Picks, and workflow coverage gaps.
Is my extension list uploaded to a server?
No. The audit runs entirely locally in the browser. There is no sign-in, no analytics script, and no remote audit API. The pasted extension list is not uploaded anywhere and stays in your browser.
What does the audit check for?
The audit compares installed GitHub CLI extensions against the GitHub CLI Extension Atlas catalog and shows: installed extensions already reviewed in the atlas, installed extensions not listed yet, missing Top Picks, workflow coverage gaps, and copyable install commands for missing workflow recommendations.
Why use this instead of gh extension search?
gh extension search is useful when you know what you're looking for, but less useful for comparison questions like which terminal dashboard to try first, whether you need a notification tool if you already have a dashboard, which extension is for Actions operations versus statistics, or if a branch cleanup tool fits your risk tolerance. The atlas answers comparison questions with reviewed catalog entries, Top Picks, comparison guides, and workflow recommendations.
What is the goal of using this audit?
The goal is not to install every recommended extension. The goal is to make the next install decision smaller and easier to review by understanding what you already have, what's missing for your workflows, and which extensions are the first-choice recommendations.
What data is included in the catalog JSON?
Each entry in the catalog JSON includes repository, category, install command, best-fit use case, avoid-if note, license, archived status, maintenance status, and verification date. This makes it usable by scripts, documentation tools, or coding agents needing current extension metadata.
Does the atlas review or endorse extension code?
No. Maintainers only verify that catalog entries are complete and correctly formatted. They do not review, audit, endorse, or support the extension code itself. The atlas focuses on installability, maintenance signals, metadata corrections, and comparison notes.
What are Top Picks in the atlas?
Top Picks are the first-choice workflow recommendations in the atlas. For example, for daily GitHub triage the atlas points to gh-dash first because it covers PRs, issues, and notifications in one terminal dashboard. The audit shows which Top Picks you're missing so you can prioritize installs.
How does the atlas handle overlapping tools?
The atlas provides comparison guides between overlapping tools. For branch cleanup, it compares tools like gh-poi, gh-branch, gh-clean-branches, gh-tidy, and gh-worktree because they sound related but solve different habits and risk profiles. For GitHub Actions, it separates different jobs into different extensions.
What feedback does the author want on the atlas?
The author is mainly looking for factual corrections and missing-extension suggestions: inaccurate descriptions, wrong categories, misleading maintenance labels, better comparisons between overlapping tools, and useful GitHub CLI extensions missing from the catalog. If you maintain an extension and the atlas describes it poorly, a short correction is enough.