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.

2

datasets available to search

ShareScore release 0.9.0

Reset

Dataset results

2 results for “javascript code”

Learn how ShareScore rates datasets ↗
zenodo40/100

Mining Rule Violations in JavaScript Code Snippets

<p><strong>Content of this repository</strong><br> This is the repository that contains the scripts and dataset for the MSR 2019 mining challenge</p> <p>Github Repository with the software used : <a href="https://github.com/urielfcampos/linting-js-codesnippets">here</a>.<br> =======</p> <p><strong>DATASET</strong><br> The dataset was retrived utilizing google bigquery and dumped to a csv<br> file for further processing, this original file with no treatment is called jsanswers.csv, here we can find the following information :<br> 1. The Id of the question (PostId)<br> 2. The Content (in this case the code block)<br> 3. the lenght of the code block<br> 4. the line count of the code block<br> 5. The score of the post<br> 6. The title</p> <p>A quick look at this files, one can notice that a postID can have multiple rows related to it, that&#39;s how multiple codeblocks are saved in the database.</p> <p><strong>Filtered Dataset:</strong></p> <p><strong>Extracting code from CSV</strong><br> We used a python script called &quot;ExtractCodeFromCSV.py&quot; to extract the code from the original csv and merge all the codeblocks in their respective javascript file with the postID as name, this resulted in 336 thousand files.</p> <p><strong>Running ESlint</strong><br> Due to the single threaded nature of ESlint, we needed to create a script to run ESlint because it took a huge toll on the machine to run it on 336 thousand files, this script is named &quot;ESlintRunnerScript.py&quot;, it splits the files in 20 evenly distributed parts and runs 20 processes of esLinter to generate the reports, as such it generates 20 json files.</p> <p><strong>Number of Violations per Rule</strong><br> This information was extracted using the script named &quot;parser.py&quot;, it generated the file named &quot;NumberofViolationsPerRule.csv&quot; which contains the number of violations per rule used in the linter configuration in the dataset.</p> <p><strong>Number of violations per Category</strong><br> As a way to make relevant statistics of the dataset, we generated the number of violations per rule category as defined in the eslinter website, this information was extracted using the same &quot;parser.py&quot; script.</p> <p><strong>Individual Reports</strong><br> This information was extracted from the json reports, it&#39;s a csv file with PostID and violations per rule.</p> <p><strong>Rules</strong><br> The file Rules with categories contains all the rules used and their categories.</p> <p>&nbsp;</p>

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

All Your Script Are Belong to Us: Collecting and Analyzing JavaScript Code from 10K Sites for 9 Months

<p>We present a massive dataset (~2 TB) of client-side JavaScript code. Specifically, we have collected and stored on adaily basis JavaScript code from Alexa&#39;s Top 10000 web sites (~7.5 GB per day) for nine consecutive months. Our collection involved both inline scripts extracted from each web site&#39;s main page and external scripts linked from it. In order to aid researchers identify similar scripts and examine their popularity and evolution, we have produced hashes that represent the scripts&#39; logical structure. Furthermore, we have analyzed the resulting dataset with well-established static analysis tools, generating additional metadata including reports with quality bugs and vulnerable libraries.</p>

opencc-by-4.0Mar 2019View 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