Skip to main content
Powered by ShareScore

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.

207

datasets available to search

ShareScore release 0.7.1

Reset

Dataset results

207 results for “github”

Learn how ShareScore rates datasets ↗
zenodo36/100

Vignette dataset for RWireX (GitHub)

<div> <p>This repository contains a dataset for a vignette of the RWireX software, which is available via Github at <a href="https://github.com/RippeLab/RWireX">https://github.com/RippeLab/RWireX</a>. RWireX is a computational tool for analyzing co-accessibility in single-cell ATAC-seq data, implemented as an extension of the ArchR package. It offers two workflows: a single-cell approach to identify autonomous links of co-accessibility (ACs) and a metacell approach to detect domains of contiguous co-accessibility (DCs). With the dataset provided in this archive, both workflows and the associated visualization can be conducted as described in the <a href="https://github.com/RippeLab/RWireX/wiki">RWireX wiki</a>.</p> </div>

opencc-by-4.0Jul 2024View details →
zenodo36/100

Structured Information on State and Evolution of Dockerfiles on GitHub

<p>Docker containers are standardized, self-contained units of applications, packaged with their dependencies and execution environment. The environment is defined in a Dockerfile that specifies the steps to reach a certain system state as infrastructure code, with the aim of enabling reproducible builds of the container. To lay the groundwork for research on infrastructure code, we collected structured information about the state and the evolution of Dockerfiles on GitHub and release it as a PostgreSQL database archive (over 100,000 unique Dockerfiles in over 15,000 GitHub projects). Our dataset enables answering a multitude of interesting research questions related to different kinds of software evolution behavior in the Docker ecosystem.</p>

opencc-by-4.0Mar 2018View details →
zenodo36/100

Commits modifications from 61 projects hosted in Github's repositories

<p>This dataset contains data from 61 opensource projects that can be found in github repositories.The data contains informations about:</p> <ul> <li>committer name</li> <li>committer email</li> <li>modification type - changed, removed or created</li> <li>modified files</li> <li>commit comments</li> <li>commit date</li> </ul> <p>&nbsp;</p> <p>This dataset references 299 major version software, developed in five different programming languages. These languages are:</p> <ul> <li>C++</li> <li>Java</li> <li>Javascript</li> <li>Python</li> <li>Ruby</li> </ul> <p>The dataset was used in my&nbsp;undergraduate thesis</p>

opencc-by-nc-4.0Nov 2018View details →
zenodo36/100

Conceptual Coupling Values - Github Projects Dataset

<p>A Dataset that contains conceptual coupling measures obtained on 61 opensource projects hosted in github.The conceptual coupling measure was calculated by 18 diferent ways. A way is called model. There are 299 software major version colected to calculate these values.</p> <p>To understand how each model was applyed, see the label meaning:</p> <ul> <li>Yco: Use code comment</li> <li>Nco: No use code comment</li> <li>Yca: Divide tokens by CamelCase</li> <li>Nca: no divide tokens by CamelCase</li> <li>Ns: no stemming tokens low frequency occurrence</li> <li>Ys: stemming tokens low frequeny occurrence</li> <li>Qth: remove third quantile&nbsp;</li> <li>Qfi: remove first quantile</li> <li>Lsi: Latent Semantic Indexing</li> <li>TFIDF: term frequency - inverse document frequency</li> <li>Naive: Term-Frequency</li> </ul> <p>All projects are from github and developed in the following language:</p> <ul> <li>C++</li> <li>Java</li> <li>Javascript</li> <li>Python</li> <li>Ruby</li> </ul> <p>This dataset also contains the following resources:</p> <ul> <li>Commits between those project versions</li> <li>List of versions used in this study</li> <li>Scripts used in some works</li> </ul>

opencc-by-nc-4.0Nov 2018View details →
zenodo36/100

Code diffs and commit messages from top1000-2000 Java projects in GitHub

<p>This dataset contains pairs &lt;code changes, commit message&gt; from top 1000-2000 Java projects in GitHub via&nbsp;<a href="https://developer.github.com/v3/">GitHub Developer API</a>.</p> <p>The structure of&nbsp;files is as follows:</p> <ul> <li>&lt;repository-id&gt;.&lt;repository-name&gt;/&nbsp; &nbsp; &nbsp; &nbsp;# Each directory contains commits of one project. <ul> <li>&lt;commit-id&gt;.&lt;commit-sha&gt;/&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; # Each directory contains one commit information, and<br> &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;# the commit-sha is the primary key of this commit in GitHub.&nbsp;<br> &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;# The children in this directory&nbsp;have 3 types: the file<br> &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;#&nbsp;&quot;commit_msg&quot;, multiple directories &quot;&lt;filename&gt;&quot;, and the file<br> &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;#&nbsp;&quot;error&quot;.&nbsp; <ul> <li>commit_msg&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;# This file contains one line, representing the commit<br> &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;#&nbsp;message.&nbsp;</li> <li>&lt;filename&gt;/&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; # The&nbsp;name of this directory is the changed file name. <ul> <li>patch&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;&nbsp;# The code diffs of this &lt;filename&gt;, describing<br> &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; #&nbsp;which lines are added and which lines are<br> &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; #&nbsp;removed with some same lines context.</li> </ul> </li> <li>&lt;filename&gt;/ <ul> <li>patch</li> </ul> </li> <li>error&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;# This file contains&nbsp;the error message when crawling<br> &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; #&nbsp;from GitHub. If this file exists, the directories<br> &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; #&nbsp;&lt;filename&gt; will not exist.&nbsp;&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;</li> </ul> </li> </ul> </li> </ul>

opencc-by-4.0Jan 2019View details →
zenodo36/100

Macro-scale analysis of biodiversity-ecosystem functioning relationships in lakes (github repository)

<p>National Lakes Assessment biodiversity-ecosystem functioning relationships across the continental United States. This is an archived version of a github repository, containing data and R code. The repository can also be found online https://github.com/cont-limno/NLA-Diversity-.</p>

opencc-by-4.0Sep 2019View details →
zenodo36/100

Data supporting CeresBarros/TrophicNetRobWF GitHub repo

Open the record for dataset details and reuse information.

opencc-by-4.0Aug 2024View details →
zenodo36/100

Introduction to Publishing Quarto Pages on GitHub

<p>This session walks through how to publish quarto pages using Visual Studio Code and GitHub. Several concepts are walked through, including webpage basics, branches, and pull requests. The demonstration also includes an overview of how TOPTSCHOOL promotes open science, the data science lifecycle, and how to apply what is learned in the TOPSTSCHOOL modules to different topics. The video can also be accessed through YouTube by clicking <a href="https://www.youtube.com/watch?v=t-rsP_xG5Bo" target="_blank" rel="noopener">here</a>.</p>

opencc-by-4.0Sep 2024View details →
zenodo36/100

GitHub Pull Request Demonstration by Alexandr Smagin

<p>In this demonstration, NLU student Alexandr Smagin walks us through pull requests for the TOPS SCHOOL GitHub repository. You can watch the video below or find a link in the 'Additional details' section.</p>

opencc-by-4.0Oct 2024View details →
zenodo36/100

MCMC Traces for GitHub repo "JuBiotech/petase-paper"

<p>Additional MCMC data to re-run analyses from https://github.com/JuBiotech/petase-ts-paper. To use the existing notebooks, please clone the GitHub repository and download and unzip this folder. Afterwards, merge this dataset and its folder structure with the existing folder "data_analysis" of the repo.</p>

opencc-by-4.0Oct 2024View details →
zenodo36/100

Repository contents of 5 GitHub Collections

<p><a href="https://github.com/collections" target="_blank" rel="noopener">Github Collections</a> are a section within the GitHub platform where repositories are collected and organized into thematic collections curated by GitHub.</p> <p>These collections group popular or prominent projects within specific areas such as Machine Learning, Web Development, Data Science, Computer Security, and many other categories of technological interest. The goal is to provide users with repository data that allows to analyze different metrics, such as repository size, filetype used or popularity, among others.</p>

opencc-by-nc-sa-2.0Nov 2024View details →
zenodo36/100

GREED: GitHub Repositories and Descriptions

<p><strong>GREED&nbsp;</strong>is dataset with metadata extracted from GitHub repositories (data collected through GitHub REST API) with Python and Jupyter Notebook as programming languages,&nbsp;more than five stars, and created in 2019 and 2020. In the <strong>final </strong>folder, the&nbsp;repositories descriptions are cleaned and filtered using natural language processing (NLP) techniques. The data is separated by programming language and year.</p> <p>In summary, this dataset contains:</p> <ul> <li><strong>102,358&nbsp;</strong>repositories (<strong>original</strong>);&nbsp;<strong>58,911&nbsp;</strong>repositories (<strong>final</strong>)</li> <li><strong>2&nbsp;</strong>programming languages</li> <li><strong>2&nbsp;</strong>creation years&nbsp;</li> </ul>

opencc-by-4.0Jul 2021View details →
zenodo36/100

DocMine: A Software Documentation-Related Dataset of 950 GitHub Repositories

<p>DocMine dataset consists of textual information collated from multiple software artifacts, across 950 GitHub Repositories. It also consists of probable percentage contribution of text in each software artifact towards different documentation types in each repository, accompanied by metadata information about the repository such as stargazer count, number of pull requests, commits, issues and other files analyzed.</p>

opencc-by-nc-sa-4.0Jan 2021View details →
zenodo36/100

Replication Package for the paper: "Caracterizando a evolução de software de contratos inteligentes: Um estudo exploratório-descritivo utilizando GitHub e Etherscan"

<p>This is the replication package for the paper &quot;Caracterizando a evolu&ccedil;&atilde;o de software de contratos inteligentes: Um estudo explorat&oacute;rio-descritivo utilizando GitHub e Etherscan&quot;. The paper was originally published in the VEM workshop, the prime Brazilian workshop for software Visualisation, Evolution and Maintance.</p> <p>&nbsp;</p> <p>The source code we used to perform the study is available at:&nbsp;https://github.com/gesid/smart-contracts-software-evolution. Please note that the current version of the code on Github may have evolved from the time we first ran the study. For the exact version of the code used to run the study, please refer to the code provided in this replication package.</p> <p>&nbsp;</p> <p>We provide a single .zip file with a few folders inside.</p> <p>- etherscan_contracts: the source code files for the smart contracts as obtained from Etherscan. We provde both the original versions and the ones without comments;</p> <p>- github_data: the source code files as extracted from the smart contracts&#39; repositories on github;</p> <p>- repositories_insights: our data analysis and main results;</p> <p>- research_source_code: the code we used to run our mining, preprocessing, analyses etc;</p> <p>- results_combinations: the similarity values for the combination of .sol files compared to the Etherscan files.</p>

opencc-by-4.0Aug 2021View details →
zenodo36/100

Readme files in 16,000,000 public GitHub repositories (October 2016)

<p>Format</p> <p>index.csv.gz - CSV comma separated file with 3 columns: &lt;repository name&gt;, &lt;flag&gt;,&lt;readme file name&gt; For example: src-d/go-git,s,README.md</p> <p>The flag is either "s" (readme found) or "r" (readme does not exist on the root directory level). Readme file name may be any from the list:</p> <p>"README.md", "readme.md", "Readme.md", "README.MD", "README.txt", "readme.txt", "Readme.txt", "README.TXT", "README", "readme", "Readme", "README.rst", "readme.rst", "Readme.rst", "README.RST"</p> <p>100 part-r-00xxx files are in "new" Hadoop API format with the following settings:</p> <ol> <li> <p>inputFormatClass is org.apache.hadoop.mapreduce.lib.output.SequenceFileOutputFormat</p> </li> <li> <p>keyClass is org.apache.hadoop.io.Text - repository name</p> </li> <li> <p>valueClass is org.apache.hadoop.io.BytesWritable - gzipped readme file</p> </li> </ol>

opencc-by-nc-4.0Feb 2017View details →
zenodo36/100

Sets of mutually similar public GitHub repositories (October 2016)

<p>The format is JSON, the list of lists. Each list is the group of very similar repositories (Weighted Jaccard Similarity threshold 0.8~0.9).</p>

opencc-by-nc-4.0Dec 2016View details →
zenodo36/100

Programming language keyword frequencies extracted from 16,000,000 public GitHub repositories (October 2016)

<p>Origin</p> <p>16,000,000 repositories on GitHub as of October 2016, classified with github/linguist and parsed with Pygments. Token.Keyword tokens were filtered and MapReduce-d. Fuzzy duplicate repositories were discarded.</p> <p>Some languages, e.g. Haskell, are parsed wrong, resulting in <strong>many</strong> keywords. Still they were not removed since we are not familiar with such languages.</p> <p>Format</p> <p>Triples [language name]\t[keyword]\t[frequency]</p> <p>Tabs and new lines in keywords are escaped as \t and \n respectively.</p>

opencc-by-nc-4.0Feb 2017View details →
zenodo36/100

Do Developers Present Proficient Code Snippets in Their README Files? An Analysis of PyPI Libraries in GitHub

<p><strong>Abstract:</strong><br> A README file plays an essential role as the face of a software project and the initial point of contact for developers in Open Source Software (OSS) projects. The code snippet is one of the most important contents in the README file for demonstrating the usage of software and APIs. Presenting easy to comprehend code snippets are preferred by developers to quickly understand the usage and features of the software. However, README files may contain proficient code snippets due to readability and performance reasons. In this paper, we first investigate the prevalence of each competency level of Python code snippets in the README files. Then, we analyze the relationships between the usage of proficient code snippets and topics of libraries. From our empirical study on 1,620 README files of PyPI libraries, we find that developers mainly present 92% of basic elements and 7% of independent elements in code snippets of the README files. However, developers may present proficient elements in code snippets for Application Framework, Quality Assurance, and User Interface libraries. Thus, we encourage developers to (i) write basic README files to attract more newcomers or (ii) write proficient README files to introduce effective usage of PyPI libraries.</p>

opencc-by-4.0Nov 2022View details →
zenodo36/100

[Github Sample Dataset] Microbiota dictate T cell clonal selection to promote graft-vs-host disease after stem cell transplantation

<p>[Github Sample Dataset]. This is an accompanying data set for the github repository &quot;<em>https://github.com/acyeh-lab/2023/tree/main/tcr-simulation&quot; referred to in &quot;</em>Non-genetic determinants of clonotypic T cell expansion following stem cell transplantation&quot; by Yeh AC et al.</p>

opencc-by-4.0May 2023View details →
zenodo36/100

Open-source Software Governance Documentation Dataset on GitHub

<p>This dataset contains 710 GitHub-hosted OSS projects, which contain a governance file in the root directory of the project. It also contains commits, issues, and comments on each project.</p>

opencc-by-4.0Jan 2023View details →

ScienceDex guides

Understand access before you commit

These curated guides explain access requirements, typical timelines, costs, and reuse considerations for widely used research datasets.

Compare curated 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.

allen-brain-atlas
neuroscienceopenDocumentation, web resources, and API references are available online.
Last verified 2026-04-30Open record

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.

abode-home-cage
behavioral-neuroscienceopenThe DataShare record exposes download links for annotations, documentation, license text, and the zipped per-snippet data directory.
Last verified 2026-04-30Open record

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.

dandi-nwb
electrophysiologyopenPublished Dandiset metadata and archive endpoints are available through the production DANDI API.
Last verified 2026-04-30Open record

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.

ibl
behavioral-neuroscienceopenPublic sessions can be searched and loaded from the IBL public data server through ONE.
Last verified 2026-04-29Open record

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.

openneuro
neuroscienceopenPublished datasets are available on demand over the internet.
Last verified 2026-04-29Open record