Update README.md
Browse files
README.md
CHANGED
|
@@ -20,4 +20,29 @@ dataset_info:
|
|
| 20 |
---
|
| 21 |
# Dataset Card for "AGabs_finetuning"
|
| 22 |
|
| 23 |
-
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 20 |
---
|
| 21 |
# Dataset Card for "AGabs_finetuning"
|
| 22 |
|
| 23 |
+
Dataset is imported from CodeXGLUE and pre-processed using their script.
|
| 24 |
+
Where to find in Semeru:
|
| 25 |
+
The dataset can be found at /nfs/semeru/semeru_datasets/code_xglue/code-to-code/Defect-detection in Semeru
|
| 26 |
+
|
| 27 |
+
CodeXGLUE -- Defect Detection
|
| 28 |
+
Task Definition
|
| 29 |
+
Given a source code, the task is to identify whether it is an insecure code that may attack software systems, such as resource leaks, use-after-free vulnerabilities and DoS attack. We treat the task as binary classification (0/1), where 1 stands for insecure code and 0 for secure code.
|
| 30 |
+
|
| 31 |
+
Dataset
|
| 32 |
+
The dataset we use comes from the paper Devign: Effective Vulnerability Identification by Learning Comprehensive Program Semantics via Graph Neural Networks. We combine all projects and split 80%/10%/10% for training/dev/test.
|
| 33 |
+
|
| 34 |
+
Data Format
|
| 35 |
+
Three pre-processed .jsonl files, i.e. train.jsonl, valid.jsonl, test.jsonl are present
|
| 36 |
+
|
| 37 |
+
For each file, each line in the uncompressed file represents one function. One row is illustrated below.
|
| 38 |
+
|
| 39 |
+
func: the source code
|
| 40 |
+
target: 0 or 1 (vulnerability or not)
|
| 41 |
+
idx: the index of example
|
| 42 |
+
Data Statistics
|
| 43 |
+
Data statistics of the dataset are shown in the below table:
|
| 44 |
+
|
| 45 |
+
#Examples
|
| 46 |
+
Train 126,477
|
| 47 |
+
Dev 15,809
|
| 48 |
+
Test 15,810
|