Backend
How Well Do SAST Tools Work Across Languages? An Empirical Study Using OCPP Implementations
arXiv cs.CR0 views
arXiv:2611.14362v1 Announce Type: new Abstract: As electric vehicle (EV) adoption accelerates globally, securing electric vehicle charging station (EVCS) software becomes increasingly critical. The Open Charge Point Protocol (OCPP), widely adopted for EVCS management, places significant responsibility on developers to securely implement specifications that are subject to multiple interpretations. The variety of OCPP implementations across different programming languages provides a unique opportunity to evaluate security tooling in a real-world, multi-language context where implementation variability may introduce vulnerabilities. This study provides the first empirical evaluation of Static Application Security Testing (SAST) tool performance across multiple programming languages using OCPP implementations as a real-world test corpus. We applied both comprehensive multi-language tools (SonarQube and Semgrep) and language-specific analyzers to twelve OCPP 1.6 implementations--each written in a distinct programming language--to examine how detection patterns vary across language ecosystems. Total issues ranged from just two in Rust to 1,689 in Java. Mature programming languages like Java yielded substantially more findings than newer languages like Rust, likely because established languages have more developed SAST tool ecosystems rather than inherently worse code quality. These results suggest that developers should consider available SAST tooling when selecting implementation languages for security critical systems.
Source:https://arxiv.org/abs/2611.14362PreviousMammothDP: Private Boosted Decision Trees Ready for Trusted Hardware and Leakage-free HyperparametersNextHow wide must an eavesdropper be? Leakage of a toric-code logical bit to a strip and the Nishimori point
Related posts
Postgres 14 hits end of life on November 12
0dev.to

MySQL to Snowflake: Binlog CDC Without Kafka or Debezium, Step by Step
0dev.to
Node.js Template Ownership: 3 PDF Watermark API Decisions Before Sharing SaaS Reports
0dev.to
I Built an Open-Source Tool to Test What Happens When MCP Servers Fail
0dev.to
Streamlining complex Helm tooling reduces team overhead and administrative friction
0dev.to

100% annotation agreement can mean one labelled record out of twelve
0dev.to