Files
Open_Ultra_SAST/benchmarks/pairs/agent-vfc/README.md
T
Marius CiepluchandClaude Fable 5.1 8ab4207618 feat(pair-corpus-honesty): add vibe-py, vfc-js and agent-vfc slices with mechanism vocabulary
Tasks 1.1, 5.1, 5.2, 5.4 and the data half of 5.3.

- mechanisms.toml: closed vocabulary v1 (20 ids) every expected row cites.
- vibe-py: 35 Real-Vuln-Benchmark pairs (Apache-2.0), human provenance only
  because the LLM-generated repositories carry no license (escalated).
- vfc-js: 17 Node fix-commit pairs harvested upstream (MIT/Apache-2.0),
  SecBench.js itself is not vendored (no license); sinks derived on 13/17.
- agent-vfc: 29 agent-trailer fixes as catalog-candidates.toml plus
  REVIEW.md; the loaded catalog stays empty until a human reviews them.
- datasets.toml and README document every slice and its review status.

Co-Authored-By: Claude Fable 5.1 <[email protected]>
Claude-Session: https://claude.ai/code/session_01T7XD7x5KonMdmGRkp63EQG
2026-09-05 10:45:42 +02:00

1.0 KiB

agent-vfc slice

Security-fix commits carrying an AI coding agent co-author trailer or generation marker (Claude Code, Codex, Cursor, Copilot, Devin), in JavaScript, TypeScript, or Python. provenance = "agent". Only repositories with a stated license are vendored.

Review checklist (Req 5.3)

A recipe with reviewer = "pending" is a candidate, not a label. Before setting reviewer:

  1. The parent excerpt really contains the vulnerability the title claims (not a refactor).
  2. One mechanism from benchmarks/pairs/mechanisms.toml explains it; adjust mechanism and cwe.
  3. The fixed excerpt removes it and the change is inside the vendored function.
  4. No secret, token, or personal data is in either excerpt (run the redaction check).
  5. The license header is present and matches the repository license.

Rebuild: python benchmarks/pairs/agent-vfc/build_recipes.py --search /tmp/agents.jsonl then --from /tmp/agents.jsonl, harvest.py --slice agent-vfc --all --fetch, catalog_gen.py --slice agent-vfc.