Is It Safe to Connect a Third-Party App to Your GitHub Account?

The honest answer is: it depends on what the app does, not what it promises. Here's exactly what happens when you use Rithub's "Continue with GitHub" and import flow — read-only, checkable, with the specific things it never touches.

Why the scope itself isn't the full answer

GitHub's own docs point out a real limitation: classic OAuth apps can't scope code access to read-only — requesting the repo scope grants both read and write, even if the app only intends to read. GitHub Apps can request finer, truly read-only permissions, but either way, the scope grant tells you what's possible, not what the app actually does. That's a judgment call about the specific app, not something a permission dialog settles for you.

What Rithub's GitHub import does

ReadsNever writes or touches
Code + full commit history, branches, tagsGitHub Actions configuration or run history
Issues and pull request threadsWebhook configuration
Releases, labels, milestonesRepository or Actions secrets
Wiki pagesBranch protection / repo settings

The one-time import and every later mirror re-sync (automatic, every 8 hours — see keeping a repo auto-mirrored) are both one-directional: GitHub to Rithub. Nothing is pushed back.

How to verify it instead of trusting it

  1. Import a throwaway public repo you don't care about.
  2. Check your GitHub account's audit log / security log right after — look for anything beyond the read calls above.
  3. Check the repo's own webhook and secrets settings on GitHub — unchanged.
  4. Revoke Rithub's access from GitHub's connected-apps settings whenever you want. The imported copy on Rithub stays; it's a separate repo, not a live tether back to GitHub.
See exactly what an import copies Sign up free