Files
Open_Ultra_SAST/benchmarks/pairs/vibe-py
Marius CiepluchandClaude Opus 5 d1faa04771 feat(learning-harness): declared twins and a fixture-difficulty check
The five byte-identical vibe-py twins now say so in the catalog instead of
only hashing to it, and a declared limit that names one of the unscorable
vocabulary's own reasons keeps that spelling, so `identical_twin` stays one
fact. Leave-one-out over vibe-py consequently runs on 30 rows, not 35.

The difficulty check measures three axes the corpus varies on: binding hops
from the identity source to the constrained use, registration distance, and
guard distance. Measured first, and it failed: the shared obligations
fixture reached (1, 0, 2) where the vibe-py absence rows reach (5, 2, 2).
Every fixture handler carried its own route decorator, so nothing in the
suite exercised a handler registered from another document and no binding
chain was longer than one hop -- the checker was passing on a simpler world
than the one it meets. `from_spec` closes that with the connexion shape
those rows really have. The verdict is committed beside the numbers.

Co-Authored-By: Claude Opus 5 (1M context) <[email protected]>
Claude-Session: https://claude.ai/code/session_01T7XD7x5KonMdmGRkp63EQG
2026-09-06 13:09:56 +02:00
..

vibe-py slice

Isolated Python web functions from Real-Vuln-Benchmark (Apache-2.0 benchmark; each target repository keeps its own license).

  • Vuln side: the function enclosing a labeled vulnerable finding (is_vulnerable = true).

  • Fixed twin: a false-positive trap function (is_vulnerable = false) from the same repository. The scanner must stay silent there, so silent-on-fix here measures precision on traps.

  • Provenance: human for the 26 human-authored apps, agent for the 40 LLM-generated apps. The LLM-generated repositories (kolega-ai-dev/vc-*) carry no license file, so they are never vendored (Req 5.4): build_recipes.py --pointers appends them as vendored = false rows (80 pairs over the 40 repositories, agent, review_tier = "seeded") that ousast pairs --slice vibe-py --pointers harvests into the local cache and scores (Req 10). The default run skips them with pointer_pair_skipped.

  • Caveat: the human corpus is educational and CTF style (DVPWA, VAmPI, vulpy, ...), not production code. Say so when reading numbers.

  • Matching: every row names the function; the upstream scorer tolerates ±10 lines, ours requires the detection inside the function.

  • Excerpt shape: line-range excerpts of methods keep their class indentation, so 27 of them fail stdlib ast.parse ("unexpected indent") while tree-sitter parses them with correct function ranges. parse_failed 0 rests on tree-sitter; stdlib-ast parity would need dedenting.

Rebuild: see the docstring of build_recipes.py (add --pointers for the LLM repositories). Regenerate the catalog with python benchmarks/pairs/catalog_gen.py --slice vibe-py. Maintainer only; CI never fetches.