Setup guide & token instructions click to toggle
What is this tool?
GitHub Repo Manager lets you browse, filter, and bulk-manage all your GitHub repositories from a single page. You can change visibility (public/private), archive or unarchive repos, and delete repos you no longer need — all in bulk. Everything runs locally in your browser. No backend, no data stored, no third-party services. The only external calls go to api.github.com.
What is a Personal Access Token (PAT)?
A PAT is a password-like string that lets applications access GitHub on your behalf without using your actual password. GitHub offers two types. We recommend a classic token for this tool — it's simpler to set up (just two checkboxes), works across all your repos by default, and doesn't require org opt-in. Fine-grained tokens are listed below as an alternative.
Recommended: Classic token
- Go to github.com/settings/tokens/new
- In the Note field, type a label (e.g. "Repo Manager")
- Set an Expiration date (short-lived recommended)
- Under Select scopes, scroll through the list and check these two:
- repo — "Full control of private repositories" (near the top)
- delete_repo — "Delete repositories" (further down the list)
- Click Generate token at the bottom and copy it immediately — you won't see it again
Alternative: Fine-grained token — more granular control, more steps to configure
Some orgs may not support fine-grained tokens yet.
- Go to github.com/settings/personal-access-tokens/new
- Set a Token name (e.g. "Repo Manager") and optional description
- Choose a Resource owner (your account or an org)
- Set an Expiration date (short-lived recommended)
- Under Repository access, select All repositories
- Expand the Permissions section, then under Repository permissions, set Administration to Read and write
- Click Generate token and copy it immediately
Security & privacy — how your token is protected
Your token is encrypted in transit
All requests go to https://api.github.com. HTTPS (TLS) encrypts the entire request — including the Authorization header containing your token — before it leaves your browser. No one between you and GitHub can read it.
Your token is never stored
The token is held in a JavaScript variable in browser memory only. It is never written to localStorage, cookies, disk, or sent anywhere other than GitHub's API. Refreshing or closing the page clears it completely.
No third-party calls
This tool makes zero external requests beyond api.github.com. No analytics, no tracking, no telemetry. You can verify this in your browser's Network tab.
Best practices for staying safe
- Use a short expiration when creating your token (7 or 30 days)
- Only grant the minimum scopes needed (repo + delete_repo)
- Revoke the token when you're done at github.com/settings/tokens
- Be cautious of browser extensions that could access page variables
Connect to GitHub
Paste your Personal Access Token to get started. Your token stays in browser memory only.
Tokens start with ghp_ (classic) or github_pat_ (fine-grained)
API Request Log
All filters work together and update results instantly.
- Search — type any part of a repo name (e.g. "api" or "old-project")
- Visibility — show only public or private repos
- Archived — show only archived repos, or hide them
- Role — filter by your relationship: repos you own, forked, belong to an org, or collaborate on
- Created between — enter a year in "From", "To", or both to filter by creation date. E.g. type 2020 in From and 2022 in To to see repos created in 2020, 2021, or 2022
Tip: combine filters to narrow results, e.g. "all forked repos from 2020 that are still public". Use the checkbox in the table header to select all repos on the current page, then apply a bulk action. Change repos per page (25/50/100) in the table footer.
| Name | Visibility | Archived | Role | Created | Last pushed | Stars | In use? |
|---|