Developer Best Practices - Structuring Your Repository for Static Web Apps
Aug 11, 2021April Yoho

Summary
This post addresses a security risk in Azure Static Web Apps CI/CD pipelines where the pipeline YAML file could be exposed publicly if deployed from the root of the repository. The author resolves this by moving application files to a 'src' subfolder and updating the pipeline configuration to reference this new location, thereby preventing public access to the YAML file. It also highlights the importance of repository configuration and awareness of external exposure risks.
More from the Azure Pipelines Supply Chain Security trail
- Axios npm Supply Chain Compromise – Guidance for Azure Pipelines Customers
- Automate your open-source dependency scanning with Advanced Security
- One Pipeline to Rule Them All: Ensuring CodeQL Scanning Results and Dependency Scanning Results Go to the Intended Repository
- April Patches for Azure DevOps Server and Team Foundation Server
- Introducing Pull Request Annotation for CodeQL and Dependency Scanning in GitHub Advanced Security for Azure DevOps