To be compatible with code scanning, what data format must third-party code scanning tools use for output?
Correct Answer: A
GitHub code scanning integrates with third-party static analysis tools through SARIF, the Static Analysis Results Interchange Format. A compatible analysis tool generates its findings as a SARIF file, which GitHub can process and display as code scanning alerts within the repository. GitHub supports SARIF output generated outside GitHub, including results from external CI/CD systems or security-analysis products. The results can then be uploaded to GitHub using an appropriate workflow action, API, or supported integration.
YAML is commonly used for GitHub Actions workflow configuration but is not the interchange format for code scanning findings. ESLint is an analysis tool rather than a results-exchange specification, and ECMAScript defines JavaScript language standards. Therefore, SARIF is the required output format.