Billing items

Updated at:
Copy as MD

Code Security is billed separately based on the feature modules you use. SAST (Static Application Security Testing) is billed by Credit consumption, and SCA (Software Composition Analysis) is also billed by Credit consumption.

SAST billing

SAST performs semantic analysis based on large language models and is billed in Credits. Different scan scenarios consume different amounts of Credits.

Credit consumption scenarios

The following table lists the trigger methods, scan scopes, and Credit consumption for each scan scenario.

Scan Scenario

Trigger Method

Scan Scope

Credit Consumption

Pre-Git-Commit Scan

Triggered before each commit

Code changes about to be committed

Low (incremental scan)

MR Incremental Scan

Triggered when an MR is created or updated

Code changes in the MR

Low (incremental scan)

Full Scan

Triggered after a merge to the main branch or on a schedule

Entire project codebase

High (project-level scan)

Manual Scan

Manually upload a code archive and create a scan task

Contents of the uploaded code archive

Depends on code size and defect density

Note

Actual Credit consumption depends on the code volume, scan scope, and density of defects and vulnerabilities. Incremental scans are snippet-level scans with low consumption, while full scans are project-level scans with high consumption.

SCA billing

SCA is billed based on the number of dependency packages scanned. Each dependency package consumes 50 Credits.

Note

Basic SCA scanning consumes Credits at a rate of 50 Credits per dependency package.