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.
8
datasets available to search
ShareScore release 0.9.0
Dataset results
8 results for “API usage”
Understanding API Usage and Testing: An Empricial Study of C Libraries (Artifact)
<h1>LibProbe Artifact</h1> <p>For the sake of the evaluation we preprocessed the CCScanner data to identify all clients of the libraries used in our evaluation and included those in our <code>MongoDB</code> database. This artifact will start by importing this pre-processed dependency information into a docker image which is then used for the evaluation.</p> <h2>Running the docker image</h2> <ul> <li> <p>First load the docker image by running</p> <ul> <li> <div> <div><code>gunzip -c libprobe_v2.2.tar.gz | sudo docker import - libprobe:latest </code></div> </div> </li> </ul> <p>this will load the image in your local docker images.</p> </li> <li> <p>Run a container from the image: <code>sudo docker run -it --device /dev/snd --privileged libprobe:latest /bin/bash</code> This will run a docker container which maps the pulseaudio and alsa configurations from your local host to the docker image. This is necessary to get some clients for some target libraries to build correctly. You will need an ubuntu host machine which has pulseaudio and alsa installed.</p> </li> <li>Run <code>mongod --fork --logpath /var/log/mongodb/mongod.log</code> followed by <code>mongorestore --drop --db apiusage /tmp/libprobe/database/apiusage</code> to import the results saved in the artifact. </li> </ul> <h2>Validating analysis results</h2> <ul> <li>The docker image provided does not contain any clients due to size limitations on sharing. The Mongo database contains all the results of running this evaluation.</li> <li>We provide a script <code>clone_clients.py</code> with a <code>client_repos.json </code>file in <code>/tmp/libprobe/extra</code> which can be used to clone the clients in the clients directory. </li> <li>To get the results it's possible to run <code>python3 libprobe.py analyse all -n</code> from <code>/tmp/libprobe</code>. This will overwrite the JSON files in the <code>json_files</code> directory and overwrite the graphs in the <code>graphs</code> directory.</li> </ul> <h2>Running the evaluation for one library (vorbis)</h2> <ul> <li>Download clients: Go to <code>/tmp/libprobe</code> and run <code>python3 libprobe.py download vorbis</code></li> <li>Prepare the library: <ul> <li>In /tmp/data/libraries/xiph@@vorbis run make clean then make and make check and make install.</li> <li>Copy all C files from /tmp/data/libraries/xiph@@vorbis/lib to /tmp/data/libraries/xiph@@vorbis/lib/.libs to collect accurate API coverage information.</li> </ul> </li> <li>Process the library to get the APIs and the coverage information : <code>python3 libprobe.py processlib vorbis</code></li> <li>Prepare clients for excluding sub directories that might contain vorbis library code: <code>python3 libprobe.py prepclients vorbis</code></li> <li>Get client usages: <code>python3 libprobe.py fetchusages vorbis</code></li> <li>Analyse: <code>python3 libprobe.py analyse vorbis -n</code></li> <li>(optional) Measure differential coverage for improved coverage libs: <code>python3 libprobe.py coverage vorbis</code></li> </ul> <h2>Running the evaluation for all libraries (this requires at least 300GB of disk space)</h2> <ul> <li>Download clients: Go to <code>\tmp\libprobe</code> and run <code>python3 libprobe.py download all</code></li> <li>Process the libraries: <code>python3 libprobe.py processlib all</code></li> <li>Prepare clients: <code>python3 libprobe.py prepclients all</code></li> <li>Get usages: <code>python3 libprobe.py fetchusages all</code></li> <li>Analyse: <code>python3 libprobe.py analyse all -n</code></li> <li>(optional) Measure differential coverage for improved coverage libs: <code>python3 libprobe.py coverage <library></code></li> </ul> <h2>Getting baseline coverage for libraries</h2> <p>All libraries are cloned in <code>/tmp/data/libraries</code> and clients are cloned in <code>/tmp/data/clients</code>.</p> <div> </div> <ul> <li>MBedtls: Copy the script <code>coverage_mbedtls.sh</code> from <code>/tmp/libprobe/extra</code> into the the build directory of Mbedtls <code>/tmp/data/libraries/Mbed-TLS@@mbedtls/build</code> and run <code>./coverage_mbedtls.sh</code> followed by <code>genhtml baseline.info --output-directory</code> out this will calculate the baseline coverage for mbedtls.</li> <li>FFTW: Copy the script coverage.sh from /tmp/libprobe/extra into the the root dir of FFTW and run ./coverage.sh baseline this will calculate the baseline coverage for fftw</li> <li>HDF5: Copy the script coverage_hdf.sh from /tmp/libprobe/extra into the the root dir of HDF and run <code>./coverage_hdf.sh baseline</code> this will calculate the baseline coverage for HDF.</li> <li>LMDB: Copy the script coverage_lmdb.sh from /tmp/libprobe/extra into the <code>/tmp/data/libraries/LMDB@@lmdb/libraries/liblmdb</code> and run <code>./coverage_lmdb.sh baseline</code> this will calculate the baseline coverage for LMDB.</li> <li>Zip: Copy the script coverage_zip.sh from /tmp/libprobe/extra into <code>/tmp/data/libraries/kuba--@@zip/build/CMakeFiles/zip.dir/sr</code>c and run <code>./coverage_zip.sh baseline</code> this will calculate the baseline coverage for zip.</li> <li>Vorbis: Copy the script cal_cov.py from /tmp/libprobe/extra to <code>/tmp/data/libraries/xiph@@vorbis/lib/.libs</code> and then copy all source files in the <code>.libs</code> folder by running <code>cp ../*.c .</code> from the <code>.libs</code> folder. Finally run <code>python3 cal_cov.py .</code>.</li> <li>XXhash: Copy the script coverage.sh from /tmp/libprobe/extra into /tmp/data/libraries/Cyan4973@@xxHash and run ./coverage.sh baseline this will calculate the baseline coverage for xxhash</li> </ul> <h2>Reproducing increased coverage using clients</h2> <ul> <li> <p>LMDB: The client we will use is Knot DNS.</p> <ul> <li>Change directory to <code>/tmp/data/clients/CZ-NIC@@knot</code> and run <code>autogen.sh</code>.</li> <li>Run <code>./configure --with-lmdb=/usr/local</code>.</li> <li>Then <code>make && make check</code>.</li> </ul> <p>Now go back to the LMDB directory and run</p> <ul> <li> <p>Run <code>./coverage_lmdb.sh after_knot</code>.</p> </li> <li> <p>Now go /tmp/libprobe and run <code>python3 libprobe.py coverage lmdb</code></p> </li> </ul> </li> <li> <p>VORBIS: The client we will use in SFML.</p> <p>Go to the vorbis library dir <code>/tmp/data/libraries/xiph@@vorbis</code> and run <code>make clean</code>.</p> <ul> <li>Run <code>make && make check && make install</code>.</li> <li>Go to the <code>.libs</code> folder and copy all c files there by doing <code>cp ../*.c .</code>.</li> <li>Copy <code>/tmp/libprobe/extra/cal_cov.py</code> into the <code>.libs</code> folder and run <code>python3 cal_cov.py .</code>. This will show the baseline coverage.</li> </ul> <p>Go to the SFML directory <code>/tmp/data/clients/SFML@@SFML</code>.</p> <ul> <li>Create build directory <code>mkdir build && cd build</code>.</li> <li>Run <code>cmake -DSFML_BUILD_TEST_SUITE=TRUE -GNinja ..</code>.</li> <li>Run <code>ninja</code>.</li> <li>Run <code>ctest</code>. You will see some failing tests. Thats normal as we are only interested in the Audio tests for vorbis. All Audio tests should pass.</li> </ul> <p>Go back to the <code>.libs</code> folder in vorbis and re-run the <code>cal_cov.py</code> script.</p> <ul> <li>Now go /tmp/libprobe and run <code>python3 libprobe.py coverage vorbis</code></li> </ul> </li> </ul> <ul> <li>SDL: The client we will use in UFOAI.<br> <ul> <li> <p>Go to the SDL library dir <code>/tmp/data/libraries/libsdl-org\@\@SDL</code> and then the <code>build2</code> directory where the built library is. .</p> </li> <li>Run <code>make clean && make && make install && make test</code>.</li> <li>Copy <code>/tmp/libprobe/extra/coverage_sdl.sh</code> into the <code>build2</code> folder and run <code>./coverage_sdl.sh baseline</code>. Run <code>genhtml baseline.info --output-directory out</code></li> </ul> </li> </ul> <p> Go to the UFOAI directory <code>/tmp/data/clients/ufoaiorg\@\@ufoai</code></p> <ul> <li> <ul> <li>Run <code>./configure --target-os=linux --disable-uforadiant</code> && <code>make</code>.</li> <li>Run .<code>/testall</code></li> </ul> </li> </ul> <p> Now go /tmp/libprobe and run <code>python3 libprobe.py coverage sdl</code></p> <p> </p> <ul> <li>FFTW: The client we will use in CAVA.</li> </ul> <p> Go to the FFTW3 library dir <code>/tmp/data/libraries/FFTW@@fftw3</code> and run <code>reset_cov.sh</code> then <code>make clean</code></p> <ul> <li> <ul> <li>Run <code>make && make install && make check</code>.</li> <li>Copy <code>/tmp/libprobe/extra/coverage.sh</code> into root directory of the library and run the <code>.libs</code> folder and run <code>./coverage.sh baseline</code> This will show the baseline coverage.</li> </ul> </li> </ul> <p> Go to the CAVA directory <code>/tmp/data/clients/karlstav@@cava</code>.</p> <ul> <li> <ul> <li>Run <code>./autogen.sh</code> followed by <code>./configure</code> then <code>make</code></li> <li>Run the script <code>./run_all_tests.sh</code> . </li> </ul> </li> </ul> <p> Go back to the FFTW3 library and run <code>./coverage.sh after_cava</code></p> <ul> <li> <ul> <li>Now go /tmp/libprobe and run <code>python3 libprobe.py coverage fftw3</code></li> </ul> </li> </ul>
Securing Your Crypto-API Usage Through Tool Support - A Usability Study
<p>Developing secure software is essential for protecting passwords and other sensitive data. Despite the abundance of cryptographic libraries available to developers, prior work has shown that developers often unknowingly misuse the provided Application Programming Interfaces (APIs), resulting in serious security vulnerabilities. Eclipse CogniCrypt is an IDE plugin that aims at helping developers use cryptographic APIs more easily and securely by providing three main functionalities: (1) it provides a use-case oriented view of cryptographic APIs and guides the developer through their configuration, (2) it generates the code needed to accomplish the chosen use case based on the selected choices, and (3) it continuously analyzes the developer’s code to ensure that no API misuses are introduced later. However, so far the effectiveness of CogniCrypt was never empirically evaluated. In this work, we fill this gap through a controlled experiment with 24 Java developers. We evaluate the tool’s effectiveness in reducing API misuses and saving developer time. The results show that CogniCrypt significantly improves code security and also speeds up development for cryptograph-related tasks. The feedback received during the study suggests that developers particularly appreciate CogniCrypt’s code generation. Its static-analysis is valued for keeping the code up-to-date. Yet, the further integration of generated code into a developer’s project still presents a major challenge. Nonetheless, our results show that CogniCrypt effectively helps application developers produce more secure code.</p>
Dataset of Empirical Evidence of Large-Scale Diversity in API Usage of Object-Oriented Software
<p>Dataset of Empirical Evidence of Large-Scale Diversity in API Usage of Object-Oriented Software, SCAM'13.</p> <p>https://www.monperrus.net/martin/companion-diversity-api-usages</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>
Detecting Usage of Deprecated Web APIs via Tracing: Replication Package
<p>Replication package for "Detecting Usage of Deprecated Web APIs via Tracing", published at 21st IEEE International Conference on Software Architecture (ICSA 2024)</p> <p> </p> <p>Changes from v2 to v3:</p> <ul> <li>readme.md: The requirements are now stated and explanations are given in more detail. Some typos in commands are fixed.</li> </ul> <p> </p> <p>Changes from v1 to v2:</p> <ul> <li>DATA: In addition to the intermedia data (output.json), the overall result files (results.json) are now provided as well for all example projects.</li> <li>IMPLEMENTATION: An incomplete version of the DeprecationDetector was present in v1. The new version includes extended matching functionality for specifications and improved export formatting.</li> <li>PROJECT: The server.jar in the client-server example project has been improved.</li> </ul>
This repository serves as a replication package for the research paper titled "Typestate-based Fault Localization of API Usage Violations in a Deep Learning Program"
<h2>Overview</h2> <p>This repository serves as a replication package for the research paper titled "An Approach to Detecting Usage Protocol Violations in Deep Learning Programs."</p> <h2>Benchmarks</h2> <p>Two benchmarks were utilized in the research:</p> <ol> <li> <p>Benchmark1 from NeuraLint:</p> <ul> <li>Location: <code>NLBench/SOSamples</code></li> </ul> </li> <li> <p>Benchmark2 from Humbatova et al.:</p> <ul> <li>Location: <code>HumbatovaBench/SOSamples</code></li> </ul> </li> </ol> <h2>Reproducing Results</h2> <p>To replicate the results presented in the paper, follow these steps:</p> <ol> <li>Download the NeuralStateAnalysis Zip file.</li> <li>Extract the file and navigate to the NeuralStateAnlaysis directory.</li> <li>(Optional) Install the necessary requirements by executing <code>pip install requirements.txt</code>. Note: The requirements.txt file is already available in this repository.</li> </ol> <h3>Running NeuralState on <code>NLBench</code>:</h3> <ol> <li>Navigate to the <code>NLBench</code><code>/SOSamples</code> directory.</li> <li>Open any of the programs you wish to execute.</li> <li>Set the path to the NeuralStateAnalysis directory: <code>Path-to-folder/NeuralStateAnalysis/</code></li> <li>Run the program using the command <code>python program_id</code>. Since the 'NeuralStateAnalysis(model).debug()' call is already present in all programs, you will be able to reproduce the results.</li> </ol> <h3>Running NeuralState on <code>HumbatovaBench</code>:</h3> <ol> <li>Navigate to the <code>HumbatovaBench</code><code>/SOSamples</code> directory.</li> <li>Open any of the programs you wish to execute.</li> <li>Set the path to the NeuralStateAnalysis directory: <code>Path-to-folder/NeuralStateAnalysis/</code></li> <li>Run the program using the command <code>python program_id</code>. Since the 'NeuralStateAnalysis(model).debug()' call is already present in all programs, you will be able to reproduce the results.</li> </ol>
Companion Web Page for "Empirical Evidence of Large-Scale Diversity in API Usage of Object-Oriented Software"
<p>dataset-jars-scam2013.zip:</p> <ul> <li>Content: 3 418 Jar files, which include 382 774 different types (classes or interfaces).</li> <li>Source: All Jar files present on a machine used for performing software mining experiments for 7 years.</li> </ul> <p>type-usages-20130622.zip:</p> <ul> <li>Content: All the type-usages, filtered by type of the type-usage</li> </ul> <p>Software:</p> <ul> <li>Software to extract type-usages: <a href="https://github.com/monperrus/typeusage">https://github.com/monperrus/typeusage</a></li> </ul> <p> </p> <p>Paper:</p> <pre>@inproceedings{Mendez2013, title = {Empirical Evidence of Large-Scale Diversity in API Usage of Object-Oriented Software}, author = {Mendez, Diego and Baudry, Benoit and Monperrus, Martin}, url = {<a href="https://hal.archives-ouvertes.fr/hal-00844753/file/article.pdf">https://hal.archives-ouvertes.fr/hal-00844753/file/article.pdf</a>}, booktitle = {{International Conference on Source Code Analysis and Manipulation (SCAM'2013)}}, pages = {10}, year = {2013}, doi = {<a href="https://doi.org/10.1109/SCAM.2013.6648183">10.1109/SCAM.2013.6648183</a>}, } </pre>
Dataset for PSASpotter: A Tool to Detect the Usage of Platform-Specific APIs in Python
<p>This dataset was utilized in the research paper titled "PSASpotter: A Tool to Detect the Usage of Platform-Specific APIs in Python" for publication in Mining Software Repositories (MSR). Herein, we present a concise abstract of the study.</p> <p>A <em>platform-specific API</em> is implemented for a particular platform (e.g., operating system), thus, it may not work on other platforms than the target one. Detecting the usage of such APIs is important for supporting software maintenance, as it allows maintainers to be alerted about APIs that could pose potential risks. This paper proposes PSASpotter, a tool to detect the usage of platform-specific APIs in Python systems. PSASpotter also identifies whether the platform-specific APIs are used within a defensive code, such as try/except blocks or if blocks that check the current platform. PSASpotter can support the development of novel empirical studies about the usage of platformspecific APIs in the Python ecosystem. Moreover, the defensive code detected by PSASpotter may contain alternative solutions for unavailable APIs, which can provide insights for software development and testing across multiple platforms. PSASpotter is available at: https://github.com/ricardojob/PSASpotter. </p> <p> </p> <div> <div>PSASpotter is an AST-based tool that detects API usage at the function/method level. Given a Git project, PSASpotter analyzes all Python files and exports details of platform-specific API usage. Specifically, for each usage, PSASpotter reports information about the analyzed project (name and commit), the used API (name and availability), and the usage location (filename, line, and GitHub link). In addition, PSASpotter also reports whether the usage happens within defensive code.</div> </div> <p>The tool <strong>PSASpotter</strong> is publicly available at <a href="https://github.com/ricardojob/PSASpotter">https://github.com/ricardojob/PSASpotter</a>.</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.