arXiv:2611.23967v1 Announce Type: new Abstract: The high frequency of cybersecurity incidents involving web applications highlights the importance of secure software development practices. Static Application Security Testing (SAST) tools help identify potential vulnerabilities in source code without executing the code. Integrating SAST tools into GitHub Security Actions enables security alerts to be reported during development. However, the characteristics of these alerts can make them difficult for developers with limited security expertise to understand, prioritize, and address. Many tutorials for learning web application development also involve source code with security implications. We investigated the properties of SAST alerts relevant to this learning context. We analyzed 6,609 alerts from four default GitHub Security Actions configurations across 60 Django and Spring tutorial repositories. We evaluated the alerts along four dimensions: alert volume, alert relevance, conceptual breadth, and remediation usability. Of the 6,609 alerts, 3,750 (56.7\%) targeted tutorial-related files, while 2,859 (43.3\%) targeted other repository files. The configurations triggered between 34 and 646 distinct rules, and the five most frequently triggered rules accounted for 25.2\%--68.2\% of alerts, depending on the configuration. Across configurations, 0.4\%--32.1\% of alert messages named concrete framework or code constructs, and 0\%--8.1\% met our operational criteria for remediation specificity. Overall, default GitHub Security Actions report a diverse set of security alerts, but these alerts do not consistently focus on tutorial code or provide concrete guidance for addressing the reported issues.