arXiv (All)
open access
Barriers to Using Static Application Security Testing (SAST) Tools: A Literature Review
Developers face a challenging problem with no clear solution. Modern software breaches can wreak havoc on businesses and individuals alike. With code vulnerabilities being a leading cause, securing applications must be a priority for developers. Static Application Security Testing (SAST) has the pot
Conceptio Open Archive
Analyze & explore related research in Conceptio
Connect this record directly into your research workflow or AI agent. Explore citations across open repositories, query full text, and export structured proof bundles.
This document is indexed with metadata only: full text is not available in the archive for this record. Open the official source ↗
Related documents
- Barriers to Using Static Application Security Testing (SAST) Tools: A Literature Review#632908
- Context-Based Support to Enhance Developers’ Learning of Software Security#199526
- BP: Security Concerns and Best Practices for Automation of Software Deployment Processes: An Industrial Case Study#964218
- SWE-Gate: Passing Functional Tests Is Not Enough for Software Engineering Agents#639706
- Federated Cybersecurity Testbed as a Service (FCTaaS): A framework to federate cybersecurity testbeds#363200
Record · ID 822106
Retrieved via Conceptio: every document is proof-bundled with source, license, and retrieval metadata.
Retrieved via Conceptio: every document is proof-bundled with source, license, and retrieval metadata.
Bring this data into your agent: Connect via MCP or API · 20 free credits to start · no card required
Read the Docs → · View CLI source on GitHub · Conceptio Open Knowledge Archive
Read the Docs → · View CLI source on GitHub · Conceptio Open Knowledge Archive