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.
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.
| Reads | Never writes or touches |
|---|---|
| Code + full commit history, branches, tags | GitHub Actions configuration or run history |
| Issues and pull request threads | Webhook configuration |
| Releases, labels, milestones | Repository or Actions secrets |
| Wiki pages | Branch 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.