Private repo permission errors

Wolfix lacks access to the organisation's repos

The repository belongs to an organisation and the GitHub App install was never approved by an owner, so Wolfix can see your account but not the org's repos.

48%

of cases

How to fix

A member can request the GitHub App install, but for an organisation-owned repo an owner has to approve it before Wolfix can read any contents. Until that approval lands, the repo won't show up in the picker.

To grant access:

1. Ask an organisation owner to open Settings → Third-party Access → GitHub Apps and approve the Wolfix install request.
2. In the install settings, confirm the specific repo is shared — choose Only select repositories and add it if it's missing.
3. Re-run the scan. The repo now appears in Wolfix's picker and the code scan proceeds.

The grant needs SSO authorization

The organisation enforces SAML single sign-on, and the install or token was never authorized for SSO — so it reads as valid but returns nothing.

34%

of cases

How to fix

Organisations with SAML SSO require every grant to be authorized for SSO before it can read repository contents. A grant that skips this step looks complete but still returns a permissions error during the scan.

To authorize:

1. Open your organisation's settings and find the Wolfix GitHub App (or your fine-grained token).
2. Click Configure SSO and authorize the grant for the organisation that owns the repo.
3. Re-run the scan. With SSO cleared, the code scan can read the default branch.

The fine-grained PAT is under-scoped

A fine-grained personal access token is missing the read-only Contents permission, or it points at the wrong resource owner or repo.

18%

of cases

How to fix

When you use a fine-grained PAT instead of the GitHub App, the only permission Wolfix needs is Contents: read-only — but the token also has to target the right owner and repository.

To fix the token:

1. At GitHub → Settings → Developer settings → Fine-grained tokens, open the token and set Resource owner to the organisation (or user) that owns the repo.
2. Under Repository access, choose Only select repositories and add the one repo you're scanning.
3. Under Permissions → Repository permissions, set Contents to Read-only. Save, then Configure SSO if your org requires it.
4. Paste the refreshed token into Wolfix's Connect screen and re-run the scan.