Build (Finix) · in development
What Finix can and cannot see.
Two separate GitHub connections, requested at two separate moments — identity when you sign in, repository access only later, only when you reach the generator. Signing in never grants repo access on its own.
The short version
Finix reads the one API spec file you point it at. It does not scan your repository, does not read any other file, and does not write anything back — no commits, no pull requests, no branches.
What signing in requests
✓ can
Read your GitHub username and email address — this is how we match you to a paid subscription.
✗ cannot
Read any of your repositories, code, or organisation data. No repo scope is requested at sign-in.
What installing the GitHub App requests
✓ can
Read repository contents — read-only, and only for the repositories you explicitly choose during GitHub's own install screen (all repos, or specific ones — your choice, made on GitHub's UI, not ours).
✗ cannot
Write, commit, open pull requests, or modify anything in your repositories. The App has no write permission at all.
✗ cannot
See issues, actions, packages, secrets, or any other GitHub resource — the App's only permission is repository contents, read-only.
In practice, when you run Build
You point the generator at a specific file (an OpenAPI spec) inside a repository you've already granted access to. Finix fetches that one file, generates a server from it, and returns the result. Nothing else in the repository is read, and nothing is ever sent anywhere beyond generating your output.
Uninstall the GitHub App at any time from your GitHub account's Applications settings — this immediately revokes all repository access, independent of your Finix subscription.
