#021Tutorial3 min

Choose a GitHub repository to analyze

Authorize the Hackaiz GitHub App, identify the correct repository, and review the analysis before starting.

Hackaiz team · updated 21/11/2026

Illustration: a person sets up an account on a laptop.
Illustration: a person sets up an account on a laptop. Illustrative photo, not a screenshot.

01Connect repository access, not just your login

Signing in to Hackaiz with GitHub is not the same as granting access to repository contents. Repository analysis uses the Hackaiz GitHub App and the repositories explicitly authorized for its installation. This applies to public as well as private repositories: an arbitrary GitHub link is not a substitute for that authorization. Begin in Connect and use the GitHub connection flow if your installation is not connected yet.

The confirmation offers “Confirm and continue to GitHub”. Review the installation on GitHub and authorize only the repositories needed for your work. For an organization repository, involve the person who can approve that organization’s app access if you cannot complete the installation yourself. Returning to Hackaiz should give you the connected repository selection rather than requiring you to paste a personal access token or share your GitHub password.

02Use the repository picker to avoid a name mix-up

When GitHub is already connected, use “Choose a repository to scan”. The dialog “Choose the repository to scan” provides search across the authorized repositories. Each result shows the repository name and its full owner/name identifier, together with public or private visibility, language and update information. Use the full identifier as your main cross-check, especially when your personal account and an organization both have a repository called web-app.

For example, studio/customer-portal and personal/customer-portal are separate targets even if they began from the same template. Select the one containing the code you intend to assess. A fork or an old prototype may look familiar but produce findings unrelated to the deployed product. The update information can help you notice an obvious mismatch, but it does not prove that the selected repository is what your production site currently serves.

  1. 1Open the picker from the connected GitHub area.
  2. 2Search for the intended repository and compare its full owner/name identifier.
  3. 3Check visibility and the other displayed metadata, then select the matching row.

03Selection is not permission to run everything

Choosing a row prepares that repository for the analysis journey. Review the selected target, compatible checks and confirmation before launching. Use the available choice mode when you need to deselect a family of checks; unticked checks do not run and are not billed. Work uses credits, so read any budget agreement shown in the flow rather than treating repository connection as an unlimited analysis allowance.

A repository provides source evidence, not automatic permission to contact its deployed website. If you also want website or API analysis, the exact domain needs its own DNS TXT or HTTPS-file control proof and recorded authorization. Equally, selecting code does not connect a live PostgreSQL or MySQL database. Keep those scopes separate so that the question you ask matches the evidence Hackaiz is allowed to collect.

04Fix missing access without choosing the wrong project

If the repository is absent, first check whether you connected the intended GitHub account or organization and whether the Hackaiz App installation includes that repository. Adjust the allowed repositories on GitHub, then return to Connect. Repeating a search cannot reveal a repository outside the app’s authorized scope. Do not select a similarly named public repository simply to get past an empty result.

After analysis, investigate source findings in the context of this repository. Where Hackaiz proposes code changes, they are draft GitHub pull requests. A human reviews and approves the changes, and Hackaiz never merges them automatically. Selecting a repository is therefore not approval of a future correction. Optional monitoring concerns connected systems only and should be considered separately from this one-time choice of a target.

Frequently asked questions

Was this article helpful?

Related articles