arXiv AI By S M Abdulla Al Mamun, Akif Islam, Mohd. Ruhul Ameen

Beyond QASecClaw: Agent Scaling, Verifier Feedback, and Evidence Reliability in Software Assurance

Read the original on arXiv AI →

The study investigates whether adding specialist language‑model contexts can enhance software assurance when deterministic tool evidence is already available. Five experiments were conducted using Qwen2.5‑Coder‑7B‑Instruct across Java warning controls, OWASP Benchmark, Defects4J test generation, SV‑COMP assertion verdicts, and misleading evidence packages. Results show that increasing context count does not improve unsafe clearance, that verifier feedback can raise correct verdicts but also incorrect ones, and that models reject most counterexamples while scope checks classify packages accurately, supporting deterministic evidence admission but highlighting limits in verdict aggregation and feedback interpretation.

Machine-generated by The Flow from the publisher's headline and feed description — not written or checked by a human. The full article lives at arXiv AI.

arXiv AI
6d ago

Who Verifies the Builder? Toward Independent Assurance for Agent-Produced Software

The paper discusses the need for independent assurance when coding agents produce both software and its correctness evidence. It identifies four gaps—requirement, conformance, evaluation, and model—between stakeholder intent and production, and proposes a verification framework that separates building from verifying. The framework introduces a Verification Contract, a specification-first phase, and an implementation-aware phase using mutation analysis, property-based testing, and fuzzing, and is evaluated in a study showing that an external verifier detected more seeded faults than the builder’s own tests.

By Sion Israel Sion, Alain April
arXiv AI
Sep 25

SWE-Prometheus: Measuring Engineering Governance Improvements in Real-World Repositories

SWE-Prometheus is a new benchmark that evaluates large language model coding agents on the broader task of improving repository engineering governance, rather than just fixing individual issues. It presents fixed snapshots with open-ended objectives, requiring agents to identify risks, prioritize interventions, and verify changes across six governance dimensions. The benchmark includes 60 repositories and reports metrics such as Normalized Governance Improvement and behavior‑breakage rates, providing a nuanced view of how different models affect governance artifacts and execution‑backed improvements.

By Jiajun Wu, Leixin Sun, Zihan Tan, Yitao Liu, Shuo Li, Jiaru Qian, Shanghaoran Quan, Chuangxin Zhao, Yangxu Liao, Yang Liu, Bin Chong, Guancheng Wan