Find research datasets worth reusing
Search datasets from major research repositories and use ShareScore to quickly assess how well each record supports discovery, access, and reuse.
47
datasets available to search
ShareScore release 0.9.0
Dataset results
47 results for “Static Analysis”
Dataset for Quieting the Static: A Study of Static Analysis Alert Suppressions
<h2><strong>Dataset for Quieting the Static: A Study of Static Analysis Alert Suppressions</strong></h2><p>This is the dataset for our empirical study on the practices of software bug suppression in open source projects.</p><h3><strong>Directory Structure</strong></h3><ul><li>./categorization: Contains the categorization spreadsheet data of sampled suppressions in csv format, as well as the raw JSON sample.</li><li>./categorization/html_files: Contains the annotated code fragments of the sampling process in HTML format.</li><li>./data: Contains the datasets of canonicalized configuration and annotation warning suppressions in JSON format.</li></ul><p><br> </p>
Artifact for "BDDs Strike Back - Efficient Analysis of Static and Dynamic Fault Trees"
<p>Artifact for the paper "BDDs Strike Back - Efficient Analysis of Static and Dynamic Fault Trees"</p> <p>The package contains:</p> <ul> <li>example files for all static and dynamic fault tree models</li> <li>installation instructions for the three tools</li> <li>scripts to perform the benchmarking</li> <li>detailed result tables</li> </ul>
Codes and Data for "Vertically resolved analysis of the Madden-Julian Oscillation highlights the role of convective transport of moist static energy"
<p>This file contains the analysis code and a condensed version of data to reproduce figures in the paper "Vertically resolved analysis of the Madden-Julian Oscillation highlights the role of convective transport of moist static energy". </p>
Combining dynamic and static analysis for automated grading SQL statements
<p><strong>Introduction</strong></p> <p>Our experiment was conducted in an undergraduate Relational Database course at the Australian National University. The experiment was conducted on August 10th 2018 when students enrolled in the Relational Database course started to learn relational data model and SQL. The experiment was carried out fully online for three weeks and a total of 393 students were enrolled. The students were asked to login in an online assessment platform and complete 15 exercises. This platform provided an SQLite environment in students browsers by compiling the SQLite C code with Emscripten.</p> <p>Students were allowed to submit and execute their answers in the form of SQL statements. If the execution result of the statement submitted by the student is the same as that of the reference statement, the online assessment platforms will return a feedback message indicating that the execution result is correct. During the interaction with the assessment platform, statements submitted by students were recorded and archived. Overall, our experiment had collected 12,899 statements submitted by students. To create a benchmark dataset that can be used to evaluate different grading approaches, we randomly selected 45 SQL statements submitted by students for each exercise, and asked three teaching assistants to grade them manually. Finally, we average the scores provided by the three assistants and take it as the final score of each statement. The dataset collected in this experiment is ready for public release.</p> <p>All experimental data are stored in Submission.sqlite, which is an SQLite database file. It is recommended to use software such as DB browser or SQLite expert to explore the database.</p> <p> </p> <p><strong>Datatable description</strong></p> <p> </p> <p><em><strong>exercises_result</strong></em></p> <p>This datatable stores the statements submitted by students. Based on the execution result of statement, statements were divided into three categories.</p> <ul> <li>noninterpretable: the statement is non-executable.</li> <li>partially correct: the execution result of statement is different from the expected result.</li> <li>correct: the execution result of the SQL statement is the same as the expected result.</li> </ul> <p>After analyzing the correct statements, we found that the correct set contains some statements carefully constructed by students to deceive the examination system.</p> <p>Take exercise 1 as an example, the task is to answer the following questions using SQL statements.</p> <p>Question: Assume persons who were born in the same year are the same age and there is only one youngest person (with no ties/draws) in this database, who is/are the second youngest person(s) in the database? List the id(s) of the person(s).</p> <p>The reference statement to this exercise is:</p> <pre><code class="language-sql">SELECT p.id FROM person p WHERE p.year_born = (SELECT MAX(year_born) FROM person WHERE year_born < (SELECT MAX(year_born) FROM person)); </code></pre> <p>By exploring the database or trying to execute different statements, some students found that the ID of the person who met the conditions was '00000842', so the following statement was submitted.</p> <pre><code class="language-sql">select id from person where id ='00000842'; </code></pre> <p>The execution result of the above code was correct, but it was obviously not what the tutor expected. Therefore, we identified such statements as 'cheating'.</p> <p>Table 1 Description of exercises_result table.</p> <table> <thead> <tr> <th> <p><strong>field</strong></p> </th> <th> <p><strong>desc</strong></p> </th> <th> <p><strong>datatype</strong></p> </th> </tr> </thead> <tbody> <tr> <td> <p>submission_id</p> </td> <td> <p>Submission ID</p> </td> <td> <p>INT</p> </td> </tr> <tr> <td> <p>submitted_answer</p> </td> <td> <p>statement submitted by student</p> </td> <td> <p>TEXT</p> </td> </tr> <tr> <td> <p>submission_time</p> </td> <td> <p>Submission time</p> </td> <td> <p>NUM</p> </td> </tr> <tr> <td> <p>exercise_id</p> </td> <td> <p>Exercise ID</p> </td> <td> <p>INT</p> </td> </tr> <tr> <td> <p>is_correct</p> </td> <td> <p>Mark whether the statement is correct</p> </td> <td> <p>INT</p> </td> </tr> <tr> <td> <p>student_id</p> </td> <td> <p>Student ID</p> </td> <td> <p>INT</p> </td> </tr> <tr> <td> <p>category</p> </td> <td> <p>categories of statement</p> </td> <td> <p>TEXT</p> </td> </tr> </tbody> </table> <p> </p> <p><em><strong>exercises_benchmark</strong></em></p> <p>This datatable stores the scores provided by different assistants. We randomly selected 45 SQL statements submitted by students for each exercise, and asked three teaching assistants to grade them manually. Finally, we averaged the scores provided by the three assistants as the final score of each statement.</p> <p>Table 2 Description of exercises_benchmark table.</p> <table> <thead> <tr> <th> <p><strong>Field</strong></p> </th> <th> <p><strong>comment</strong></p> </th> <th> <p><strong>datatype</strong></p> </th> </tr> </thead> <tbody> <tr> <td> <p>Submission_id</p> </td> <td> <p>Submission ID</p> </td> <td> <p>INT</p> </td> </tr> <tr> <td> <p>grade</p> </td> <td> <p>grade provided by tutor</p> </td> <td> <p>REAL</p> </td> </tr> <tr> <td> <p>tutor</p> </td> <td> <p>tutor</p> </td> <td> <p>TEXT</p> </td> </tr> </tbody> </table> <p> </p> <p><em><strong>exercises_exercise</strong></em></p> <p>This datatable stores the exercises provided by tutor.</p> <p>Table 3 Description of exercises_exercise table.</p> <table> <thead> <tr> <th> <p><strong>Field</strong></p> </th> <th> <p><strong>comment</strong></p> </th> <th> <p><strong>datatype</strong></p> </th> </tr> </thead> <tbody> <tr> <td> <p>id</p> </td> <td> <p>Exercise ID</p> </td> <td> <p>INT</p> </td> </tr> <tr> <td> <p>title</p> </td> <td> <p>Title of exercise</p> </td> <td> <p>TEXT</p> </td> </tr> <tr> <td> <p>preamble</p> </td> <td> <p>Description of exercise</p> </td> <td> <p>TEXT</p> </td> </tr> <tr> <td> <p>difficulty</p> </td> <td> <p>Coefficient of difficulty</p> </td> <td> <p>integer</p> </td> </tr> <tr> <td> <p>ref</p> </td> <td> <p>Reference statement</p> </td> <td> <p>integer</p> </td> </tr> </tbody> </table> <p> </p> <p><em><strong>database schema</strong></em></p> <p>Please refer to db_schema.pdf for the database schema used in the experiment.</p> <p> </p> <p><strong>BibTex</strong></p> <p>if you want to cite our paper:</p> <p> </p> <blockquote> <pre>@article{wang2020combining, title={Combining dynamic and static analysis for automated grading SQL statements}, author={Wang, Jinshui and Zhao, Yunpeng and Tang, Zhengyi and Xing, Zhenchang}, journal={J Netw Intell}, volume={5}, number={4}, pages={179--190}, year={2020} }</pre> </blockquote>
Are Static Analysis Violations Really Fixed? A Closer Look at Realistic Usage of SonarQube. Dataset for OSS organizations
<p>Dataset containing all rules, files and issues mined for Apache Software Foundation and Eclipse Foundation.</p>
Alert Type Frequency Assessment of Open-Source Static Analysis Tools and Codebases
<p>This includes all data needed to replicate and validate our frequency analysis of static analysis (SA) alerts produced using open-source SA tools on several OSS codebases. It includes instructions how to get and run the SA tools, a Dockerfile to conveniently get and use the SA tools, raw SA tool output, some python scripts to parse that output, parsed SA data and aggregate analyses, and SA data augmented with CERT coding rule and CWE data. </p> <p>The SA tools used:</p> <ul> <li>clang-tidy version 15.07 </li> <li>cppcheck version 2.9 </li> <li>CERT Rosecheckers </li> </ul> <p>The codebases analyzed:</p> <ul> <li>zeek version 5.1.1</li> <li>git version 2.39.0</li> <li>dos2unix version 7.4.3</li> </ul>
SATune: An Auto-tuning Approach for Configurable Static Analysis Tools
<p>Version 2.0.0 updates: Renamed tool to SATune.</p> <p>-------</p> <p>This contains both the executables and the data for our ICST 2021 submission, "SATune: An Auto-tuning Approach for Configurable Static Analysis Tools." The results are in results.tar.xz, and the SATune source code and experimental environment is is experiments.tar.xz.</p>
Evaluation Artifacts of RESTRuler, a Static Analysis Tool to Detect Design Rule Violations in OpenAPI Definitions
<p>All artifacts related to the empirical evaluation of the RESTRuler CLI, a Java-based tool to identify design rule violations in OpenAPI descriptions</p> <p>You can find the latest version here: <a href="https://github.com/restful-ma/rest-ruler-evaluation">https://github.com/restful-ma/rest-ruler-evaluation</a></p>
What really changes when developers intend to improve their source code: A commit-level study of static metric value and static analysis warning changes
<p>This is the dataset for the publication "What really changes when developers intend to improve their source code: A commit-level study of static metric value and static analysis warning changes".</p> <p>It contains a random sample of 2533 commits from 54 Java Apache open source projects classified by two researchers into perfective, corrective and other changes (manual_labels.csv). Moreover, we include static source code metrics and static analysis warnings for the 2533 changes in al_changes_gt.csv.gz.</p> <p>In addition, we include the full dataset of 125482 commits in all_changes_sebert.csv.gz with all metrics and automatic labels for every commit that was not manually labeled. The automatic labels were provided by a fine-tuned transformer model (BERT) pre-trained exclusively on software engineering data.</p> <p>We also provide the fine tuned version of the pre-trained model in seBERT_fine_tuned_commit_intent.tar.gz as well as a Snapshot of the SmartSHARK MongoDB database used in gathering the raw data in smartshark_emse.agz.</p> <p>The model can be tested live on the <a href="https://user.informatik.uni-goettingen.de/~trautsch2/emse_2021/commit_intent.html">website</a> accompanying the publication.</p>
Replication Package for "On the correlation between Architectural Smells and Static Analysis Warnings"
<div> <div> <div> <div> <div> <h1>Replication Package for the Paper: "On the Relation between Architectural Smells and Static Analysis Warnings"</h1> <h2>Authors</h2> <ul> <li>Matteo Esposito, University of Oulu, Finland</li> <li>Mikel Robredo, University of Oulu, Finland</li> <li>Francesca Arcelli Fontana, University of Milano-Bicocca, Italy</li> <li>Valentina Lenarduzzi, University of Oulu, Finland</li> </ul> <h2>Content Overview</h2> <p>This replication package contains the following materials:</p> <ul> <li><strong>Tables:</strong> Excel files that include all hypothesis testing data, including normality tests for each hypothesis.</li> <li><strong>Data:</strong> RAW Qualitas Corpus dataset and aggregated SAT output.</li> <li><strong>SAT Instructions:</strong> A PDF file providing detailed instructions for the SAT setup and execution.</li> </ul> <h2>Contact Information</h2> <p>For any issues, questions, or further assistance, please do not hesitate to contact the authors of the paper. We are here to help!</p> </div> </div> </div> </div> </div>
Experimental–Computational Analysis of Nucleation Sites for Primary Static Recrystallization
<p>This repository contains supplementary material to our paper. Specifically, the Matlab, Python,a and Shell scripts and cellular automaton source code we used to run and post-process the simulations as well as the simulation results:</p> <p><strong>MTEXEBSDMappingStructureInitialization.zip</strong><br> Specifies, using MTex v5.0.3, how we converted the measured SEM/EBSD mapping to a synthetic 2d microstructure.</p> <p><strong>SCORESourceCode.zip</strong><br> Specifies the source code of SCORE. Version 1.2.1. Demands a local HDF5 installation. MPI/OpenMP parallelized.<br> Inspect www.github.com/mkuehbach/SCORE for further details on how to compile and background to the model<br> an implementation.</p> <p><strong>ExecuteSimulations.zip</strong><br> Specifies shell scripts and UDS input files to execute the simulations. Details via these UDS files also all parameter<br> settings we used to reproduce the runs.</p> <p><strong>ComparisonXaXv.tar.gz</strong><br> Compares in summarized form, and extracted from the RXAreaFractionDepthProfile folder files, the area vs<br> volume fraction at specified time snapshots for the z= [0.0, 0.5, 1.0] RDTD section.<br> <br> <strong>Inherited_GrainSizeMicrostructure.zip</strong><br> ANG-like serial sectioning snapshot results and IPF visualization of microstructure evolution for those<br> simulation cases in which the nuclei inherited the orientation from their site.</p> <p><strong>Random_GrainSizeMicrostructure.zip</strong><br> ANG-like serial sectioning snapshot results and IPF visualization of microstructure evolution for those<br> simulation cases in which the nuclei had random orientations form the SO3.</p> <p><strong>RXAreaFractionDepthProfile.zip</strong><br> Specifies the evolution of the area fraction recrystallized with grains in cross-sectional area >=13px<br> for every RDTD layer.</p> <p>The corresponding parameterization is detailed in the *.uds input file which specifies all constitutive parameter<br> and log settings of the automaton. The simulation is executed by compiling the program and linking to<br> HDF5. The OMP_NUM_THREADS environment variable should be set to not more than 10.<br> The SCORE is executed as follows:<br> mpirun -np 1 ./score <simid> <udsfile> <KAM Ang EBSD file> 1>STDOUT.txt 2>STDERR.txt<br> <br> <strong>Profiling.zip</strong><br> Details the execution log of the automaton ie runtime individual composition of nuclei volume transformation<br> progression, interfacial area evolution, etc.</p> <p><strong>SingleGrainData.zip</strong><br> Details the volume consumption / volume gain kinetics of every single deformed / recrystallized grain.</p> <p><strong>TemperatureTimeProfile.zip</strong><br> Details the time/temperature and step profile of the numerical integration.<br> This allows to map integration time steps to simulated microstructural states.</p> <p><strong>ThreadProfilingGrowth.zip</strong><br> Details the evolution of the recrystallized volume versus time and number of active cells per thread sub-domain.</p> <p><strong>MartinPostprocessingScripts.zip</strong><br> Is a collection of Python and MTex scripts to compile the area size distribution and compute ODFs.</p>
A time-course analysis using Differential Static Light Scattering (DSLS) of purified HTT1-3144 Q23 - 2019/01/28
<p><strong>Project: </strong>Biophysical investigation of purified HTT protein samples</p> <p><strong>Experiment: </strong>A time-course analysis using Differential Static Light Scattering (DSLS) of purified HTT<sup>1-3144</sup>Q23 </p> <p><strong>Date completed:­ </strong>2019/01/28</p> <p><strong>Rationale: </strong>Time and resources in the HD field have been primarily focussed on understanding HTT aggregation looking as caspase cleavage products spanning aa. 1-586 or exon 1 spanning aa. 1-90. However, we know that HTT protein purified in its apo form is able to self-associate into larger oligomeric species and that monomer, dimer and larger species are found following FLAG-affinity chromatography as determined by size-exclusion chromatography (SEC) and SEC-multi-angle light scattering (SEC-MALS). This experiment aimed to begin to investigate how HTT self-associates and aggregates over time in a range of different conditions. </p>
Replication Package for "How Developers Engage with Static Analysis Tools in Different Contexts"
<p>This is the replication package for the paper "How Developers Engage with Static Analysis Tools in Different Contexts".</p> <p>We include all the artifacts necessary to replicate the results obtained in our paper. Specifically, we provide (i) the survey questions together with all the valid answers we received including the demographics of our respondents, (ii) the most relevant statements that we extracted from the interviews including the demographics of our interviewees, (iii) the results of the card sorting performed on the development activities where our participants adopt Static Analysis Tools, (iv) all the data related to Krippendorff’s Alpha calculation for the performed card sorting, and (v) mapping of ASATs to the "rules" categories defined by Novak et al. (2010) and script for calculating occurrence, definition, and enforcement of the different ASAT types together with input and output data. Furthermore, we include the list of links to Reddit posts and inspected open-source projects together with their inspection data and the scripts for computing the inter-rater agreement during the inspection. Finally, we provide the Github features computed for each project and script for generating the sets of projects.</p>
Dataset for the paper Exploring the Use of Static and Dynamic Analysis to Improve the Performance of the Mining Sandbox Approach for Android Malware Identification
<p><strong>Short Description: </strong>This is the dataset for the paper "Exploring the Use of Static and Dynamic Analysis to Improve the Performance of the Mining Sandbox Approach for Android Malware Identification", accepted for publication in the Journal of Systems and Software. </p> <p><strong>Link to this repository: </strong><a href="https://github.com/droidxp/paper-replication-package">https://github.com/droidxp/paper-replication-package</a></p> <p><strong>Authors of the Paper</strong></p> <ul> <li>Francisco Handrick da Costa</li> <li>Ismael Medeiros</li> <li>Thales Menezes</li> <li>João Victor da Silva</li> <li>Ingrid Lorraine da Silva</li> <li>Rodrigo Bonifácio</li> <li>Krishna Narasimhanb</li> <li>Márcio Ribeiro</li> </ul> <p><strong>Abstract</strong></p> <p>The popularization of the Android platform and the growing number of Android applications (apps) that manage sensitive data turned the Android ecosystem into an attractive target for malicious software. For this reason, researchers and practitioners have investigated new approaches to address Android's security issues, including techniques that leverage dynamic analysis to mine Android sandboxes. The mining sandbox approach consists in running dynamic analysis tools on a benign version of an Android app. This exploratory phase records all calls to sensitive APIs. Later, we can use this information to (a) prevent calls to other sensitive APIs (those not recorded in the exploratory phase) or (b) run the dynamic analysis tools again in a different version of the app. During this second execution of the fuzzing tools, a warning of possible malicious behavior is raised whenever the new version of the app calls a sensitive API not recorded in the exploratory phase.</p> <p>The use of a mining sandbox approach is an effective technique for Android malware analysis, as previous research works revealed. Particularly, existing reports present an accuracy of almost 70% in the identification of malicious behavior using dynamic analysis tools to mine android sandboxes. However, although the use of dynamic analysis for mining Android sandboxes has been investigated before, little is known about the potential benefits of combining static analysis with a mining sandbox approach for identifying malicious behavior. Accordingly, in this paper we present the results of two studies that investigate the impact of using static analysis to complement the performance of existing dynamic analysis tools tailored for mining Android sandboxes, in the task of identifying malicious behavior.</p> <p>In the first study we conduct a non-exact replication of a previous study (hereafter BLL-Study) that compares the performance of test case generation tools for mining Android sandboxes. Differently from the original work, here we isolate the effect of an independent static analysis component (DroidFax) they used to instrument the Android apps in their experiments. This decision was motivated by the fact that DroidFax could have influenced the efficacy of the dynamic analyses tools positively---through the execution of specific static analysis algorithms DroidFax also implements. In our second study, we carried out a new experiment to investigate the efficacy of taint analysis algorithms to complement the mining sandbox approach previously used to identify malicious behavior. To this end, we executed the FlowDroid tool to mine the source-sink flows from benign/malign pairs of Android apps used in previous research work.</p> <p>Our study brings several findings. For instance, the first study reveals that DroidFax alone (static analysis) can detect 43.75% of the malwares in the BLL-Study dataset, contributing substantially in the performance of the dynamic analysis tools in the BLL-Study. The results of the second study show that taint analysis is also practical to complement the mining sandboxes approach, with a performance similar to that reached by dynamic analysis tools.</p> <p> </p>
Analyzing Static Analysis Metric Trends towards Early Identification of Non-Maintainable Software Components
<p>The provided dataset contains the data used by "Analyzing Static Analysis Metric Trends towards Early Identification of Non-Maintainable Software Components", in order to evaluate the maintainability degree of a software class and identify software components that will eventually become non-maintainable.</p>
Energy Consumption Estimation of API-usage in Smartphone Apps via Static Analysis
<p>OPEN CALL FOR COLLECTING ENERGY PROFILES @ <a href="https://github.com/AbdulAli/replication-kit-msr-2023">https://github.com/AbdulAli/replication-kit-msr-2023</a></p> <p>Cite this work as:</p> <p>@inproceedings{bangash2023msr,<br> title={Energy Consumption Estimation of API-usage in Mobile Apps via Static Analysis},<br> author={Bangash, Abdul Ali and Jamal, Qasim and Eng, Kalvin and Ali, Karim and Hindle, Abram},<br> booktitle={2023 20th International Conference on Mining Software Repositories (MSR)},<br> pages={5721--5730},<br> year={2023},<br> organization={IEEE}<br> }</p> <p>This is the replication-kit of the paper published at MSR 2023.</p> <p>It includes:</p> <ul> <li>SQLite operations' benchmarks</li> <li>SQLite benchmarks' energy profiles</li> <li>The E-Factor Calculation program</li> </ul>
Reuse of static analysis rule dataset (CADD system)
<p>Reuse of static analysis rules study dataset (in Portuguese). <em>Anonymous author f</em>or double-blind review.</p> <p> </p>
Eclipse Static Analysis - 10 Java projects
<p>This dataset consists of Eclipse's static analysis performed on 10 Java projects.</p> <p>For each <em>.java</em> file of a test project, we ran a static analysis using Eclipse JDT Core allows us to retrieve all the possible function calls based on typing/imports for a given completion site). Each java project has three files structured as follows:</p> <ul> <li><strong>*.json file. </strong>The file contains all the method declarations of the project and the function calls in their body. For each function call, the file lists all the possible function call that could have been made at that place in the source code. For practical purposes, we splitted this file into two text files.</li> <li><strong>*_sequences.txt file. </strong>This file consists of all the method declaration + function call sequences in the project. The last element of each line corresponds to a completion site.</li> <li><strong>*_proposals.txt file.</strong> Each line is made of the function-call suggestions retrieved by static analysis for the corresponding line in the <em>*_sequences.txt</em> file.</li> </ul> <p>The corpus was used for the experiments in the paper <strong>Combining Code Embedding with Static Analysis for Function-Call Completion</strong>.</p> <p>Github repository to replicate the experiments: https://github.com/mweyssow/cse-saner</p>
[CTD-ES] Automatically Fixing Static Analysis Tools Violations
<p>Video <strong>in Portuguese</strong> with a short presentation summarizing some of the main points of the research conducted during my (Diego) masters' under the supervision of Prof. Dr. Rodrigo Bonifácio.</p>
Using Code Reviews to Automatically Configure Static Analysis Tools
<p>Working dataset (check traceability oracle) used in the paper</p>
ScienceDex guides
Understand access before you commit
These curated guides explain access requirements, typical timelines, costs, and reuse considerations for widely used research datasets.
Allen Brain Atlas
Allen Brain Atlas is an Allen Institute collection of brain map atlases, datasets, APIs, and analysis tools covering mouse, human, and non-human primate brain resources.
Annotated Behaviour and Observability Dataset (ABODe)
ABODe is a University of Edinburgh DataShare dataset for behavior classification in group-housed mice using home-cage video, identities, bounding boxes, ground-plate positions, and annotator labels.
DANDI Archive for NWB datasets
DANDI is a BRAIN Initiative archive for publishing and sharing neurophysiology data, including electrophysiology, optophysiology, and behavioral data packaged as NWB and related standards.
International Brain Laboratory public data
The International Brain Laboratory public data releases expose standardized mouse decision-making experiments, including Neuropixels recordings, widefield calcium imaging, behavior, and session metadata accessed through the ONE API.
OpenNeuro
OpenNeuro is a free, open platform for sharing neuroimaging datasets, with public search, dataset pages, and download paths for web, S3, DataLad, and the OpenNeuro CLI.