ismail.tasdelen commited on
Commit
eb32bea
·
1 Parent(s): 14733a0

remove README temporarily

Browse files
Files changed (1) hide show
  1. README.md +0 -129
README.md DELETED
@@ -1,129 +0,0 @@
1
- ---
2
- task_categories:
3
- - text-generation
4
- - question-answering
5
- - token-classification
6
- - other
7
- language:
8
- - en
9
- - code
10
- tags:
11
- - security
12
- - application-security
13
- - vulnerability-detection
14
- - secure-code-review
15
- - llm-evaluation
16
- - sast
17
- - owasp
18
- - cwe
19
- - ai-security
20
- - benchmark
21
- size_categories:
22
- - 100-999
23
- ---
24
-
25
- # AppSecBench Dataset Card
26
-
27
- ## Dataset Summary
28
-
29
- AppSecBench is an original benchmark of 406 vulnerable/secure code pairs spanning 12 programming
30
- languages, 18 frameworks, 34 vulnerability classes, and 5 difficulty levels. Each record is a
31
- self-contained evaluation case: a vulnerable snippet, its secure counterpart, an exploit sketch,
32
- and the "ground truth" a detector/model is expected to produce (CWE, OWASP, severity, CVSS 3.1,
33
- explainability, fix, and false-positive/false-negative priors).
34
-
35
- The dataset supports measuring whether an LLM or security tool can **detect**, **classify**,
36
- **explain**, **score severity**, **recommend a fix**, and **generate secure code** for real-world
37
- application-security weaknesses — including modern AI/LLM risks (prompt injection, RAG, MCP, agent
38
- security) and infrastructure misconfigurations.
39
-
40
- ## Data Files
41
-
42
- ```
43
- dataset/
44
- train.jsonl (434 records)
45
- validation.jsonl (69 records)
46
- test.jsonl (69 records)
47
- ```
48
-
49
- ## Supported Tasks
50
-
51
- | Task | Input | Expected output |
52
- |------|-------|-----------------|
53
- | Vulnerability detection | `vulnerable_code` | vulnerability flagged + location |
54
- | CWE/OWASP mapping | code | `expected_cwe` / `expected_owasp` |
55
- | Severity estimation | code | `expected_severity` + `expected_cvss_score` |
56
- | Exploit explanation | code | `exploitability_explanation` |
57
- | Secure fix / secure code gen | code | `expected_secure_code` |
58
- | False-positive / false-negative analysis | code | `expected_false_positive_probability` / `expected_false_negative_probability` |
59
-
60
- ## Languages & Frameworks
61
-
62
- Python, Java, JavaScript, TypeScript, Go, Rust, PHP, C#, Kotlin, Swift, C, C++ (code); plus
63
- Infrastructure-as-Code in YAML / Dockerfile / Bash. Frameworks: Flask, FastAPI, Django, Spring
64
- Boot, Express, NestJS, Next.js, Laravel, ASP.NET Core, Gin, Echo, Fiber, Android, iOS.
65
-
66
- ## Data Fields
67
-
68
- Each record is a JSON object (see `README.md` for the field list). `metadata` carries
69
- `difficulty`, `category`, `cwe`, `owasp`, `owasp_api`, `owasp_llm`, `cvss_vector`, `cvss_score`,
70
- `source`, `license`, and `schema_version`.
71
-
72
- ## Distribution (v1.1.0)
73
-
74
- - 17 languages, 18 frameworks, 27 unique CWEs, 9 unique OWASP Top-10 (2021) classes, 34 vulnerability types.
75
- - Difficulty: Beginner, Intermediate, Advanced, Expert, Real-world enterprise.
76
- - Source type: `synthetic` for all records (original, non-derived).
77
- - Full per-dimension counts: `statistics/summary.json` and `statistics/statistics.md`.
78
-
79
- ## Methodology
80
-
81
- Records are generated deterministically (`scripts/build.py`, `seed=42`) from an original catalog
82
- (`scripts/vuln_catalog.py`) and per-language generators (`scripts/generators.py`). CVSS 3.1 base
83
- scores are computed from the official FIRST formulas (`scripts/cvss.py`). See `docs/methodology.md`.
84
-
85
- ## Quality & Validation
86
-
87
- An automated QA suite (`scripts/validate.py`) enforces: JSON validity, no duplicate IDs, required
88
- field presence, enum conformance, CWE/OWASP/CVSS format + recomputation consistency, label
89
- consistency vs the catalog, `vulnerable_code != secure_code`, reference well-formedness, and real
90
- syntax/compile checks. Result for v1.1.0: **PASS (0 errors)** over 572 records. Report: `validation/validation_report.md`.
91
-
92
- ## Intended Uses
93
-
94
- - Evaluating and comparing LLMs on secure-code understanding.
95
- - Benchmarking SAST / SCA / secret-scanning / IaC-scanning tools.
96
- - Training and fine-tuning secure-coding assistants (with proper licensing).
97
- - Academic reproducible experiments in application security.
98
-
99
- ## Limitations & Out-of-Scope
100
-
101
- - Snippets are minimal/synthetic, not full applications; they isolate one weakness at a time.
102
- - Some languages are checked with heuristic balance (not compiled) when no toolchain is present.
103
- - The benchmark measures *recognition/explanation*, not end-to-end offensive capability.
104
- - Not a substitute for manual security review or threat modeling.
105
-
106
- See `docs/LIMITATIONS.md` and `docs/INTENDED_USES.md`.
107
-
108
- ## Ethical Considerations & Responsible Disclosure
109
-
110
- `docs/ETHICAL_CONSIDERATIONS.md` and `docs/RESPONSIBLE_DISCLOSURE.md`. The vulnerable code is
111
- educational, synthetic, and non-weaponized.
112
-
113
- ## Licensing
114
-
115
- MIT. Code snippets are original and provided for defensive use.
116
-
117
- ## Citation (BibTeX)
118
-
119
- ```bibtex
120
- @dataset{tasdelen2026appsecbench,
121
- title = {AppSecBench: A Comprehensive Benchmark Dataset for Application Security Evaluation, Secure Code Review, AI Security Research, LLM Evaluation, and Secure Software Engineering},
122
- author = {Taşdelen, İsmail},
123
- year = {2026},
124
- version= {1.1.0},
125
- publisher = {Hugging Face}
126
- }
127
- ```
128
-
129
- <!-- last updated: 2026-09-10T08:49:49Z -->