QFinch integration

Source control and CI integrations

Connect approved GitHub, GitLab or Bitbucket repositories, select the repositories an organisation may assess, and bind scans to the exact revision that triggered them.

Source control and CI integrations architecture and workflow

Connect approved GitHub, GitLab or Bitbucket repositories, select the repositories an organisation may assess, and bind scans to the exact revision that triggered them.

Supported workflow

  1. An organisation administrator connects the provider.
  2. QFinch records the provider installation or OAuth scope.
  3. The administrator selects permitted repositories.
  4. Signed webhooks or CI submissions create exact-revision scans.
  5. QFinch runs eligible SAST, SCA, IaC and secrets checks according to policy.
  6. Terminal status and report links return to the provider where supported.

Provider plans and permissions determine whether issues, SARIF or security-event delivery is available. Use least-privilege permissions and rotate provider credentials according to your organisation policy.

CTA: Connect a source provider

Put evidence into your security workflow.

Start with an authorised asset and an approved policy.

Start a website scan