Hi @ASingh116376 (Community Member)​ 

To perform a static scan for an API developed in MuleSoft, you can leverage Veracode's CI/CD integrations. The Veracode Platform supports static analysis scans for various technologies.

Here's how you can approach it:

1. Understand the Packaging Requirements: Veracode's static analysis requires your application to be packaged in a specific way. For MuleSoft APIs, you'll need to ensure your project is correctly built and packaged. Refer to the packaging requirements for detailed guidance on how to prepare your application for scanning.
2. Integrate with CI/CD Pipelines: Veracode offers integrations with popular CI/CD tools. You can integrate static analysis into your build servers and release management processes. The documentation lists various integrations, such as Jenkins, Azure DevOps, GitLab, and GitHub Workflow Integration, which can help automate your scanning process. You can refer to the CI/CD integrations page for a comprehensive list and setup instructions.
3. Use Pipeline Scan: For more direct integration within your pipelines, consider using Veracode's Pipeline Scan. This allows you to run static analysis scans locally or within your CI/CD pipelines. You can find more information and setup instructions in the Pipeline Scan documentation.
4. Veracode CLI: The Veracode CLI can also be integrated with your CI/CD pipelines to perform static analysis. This involves adding a job to your pipeline that runs the veracode static scan command. Refer to the Integrate Static Analysis with the CLI documentation for examples and configuration details.

To get started, I recommend reviewing the packaging requirements specific to your MuleSoft API project to ensure it's prepared for scanning. Then, explore the CI/CD integrations or Pipeline Scan options to integrate Veracode's static analysis into your development workflow.