Skip to main content
Run full repository scans. To enforce security policies before deployment, use the CI security pipeline example.

1. Add your token

  1. Connect your repository and enable SAST, SCA, and secrets in Analysis Configuration.
  2. Create a CodeAnt token with the Codeant CI/CD role and access to this repository.
  3. In GitHub, open Settings → Secrets and variables → Actions → New repository secret. Save it as CODEANT_TOKEN.

2. Add the workflow

Save as .github/workflows/codeant-scan.yml. Replace main with your target branch.
.github/workflows/codeant-scan.yml
To block deployment, configure full-code quality gates and set quality_gate: 'true'. Fork PRs are skipped because GitHub does not provide repository secrets.

3. Run and download

  1. Merge the workflow onto your default branch.
  2. Open Actions → CodeAnt full repository scan → Run workflow.
  3. Open the completed run. Under Artifacts, download codeant-results.
The archive contains JSON findings, SARIF, and JUnit XML. The action does not generate CSV/PDF.

Inputs

Enable the selected analyses in CodeAnt; scanners selects returned results. antipatterns returns duplicate-code results. Include patterns take precedence over exclusions.

Runner data flow

The runner sends the token, repository, commit, branch, provider URL, and file filters to CodeAnt over HTTPS. CodeAnt fetches the repository server-side and returns reports. The action does not upload the runner’s source checkout or local Docker image.

Troubleshooting