DocumentationCCASigned
CCA limits
What a CCA scan covers, what it returns and where its limits are: scope, scan time, reuse, request limits, output formats, languages and rubric versions.
What a scan through Canine Code Analyzer (CCA) covers, what it returns and where its limits are. Prices, the free lines, credit and subscriptions are on CCA's pricing page.
| Limit | Value |
|---|---|
| What is scanned | The latest pushed commit of the repository's default branch, never local changes |
| Repositories | Connected through GitHub, GitLab, Bitbucket or Azure DevOps in the CCA console, or added by name if public |
| Scan time | Minutes, depending on the repository's size and build |
| The scanner | The full scanner, including the full security scan, on every plan |
| Reused result | 0 lines charged when the commit, engine version, rubric version and configuration are all unchanged |
| Version upgrade | An engine or rubric upgrade always scans again |
| Not enough lines | A scan that neither the subscription nor the credit covers is refused before it starts (402) |
| Request rate | One request rate for every plan, counted across all of an organisation's keys, there to stop misuse; past it, 429 |
| Output formats | JSON over the API, SARIF per run, and a signed evidence bundle per run |
| Languages | The live language list says which languages are read and how deeply |
| Rubric versions | Every rubric version stays published, unchanged, at codeassuranceindex.info, and every result names the one it was scored under |
Every call and its answers are in the API reference.
Document recordSigned
- Version
- v1
- Published
- 2 November 2026
- Signed by
- Jimmy Borchsigned with a login · 1 November 2026
- sha256
- 350f382ef7ab40eb47d6388dae60d0fe
7ea6e5d68b98ed44ab3396b6be92ad2c