Skip to content
Dataset · CODING

Coding Dataset

Two code sub-collections: independently authored DSA problem-solution pairs across seven languages, and production Legacy Codebases with full git history across fourteen industries.

DSA problems
12K
DSA problems
Legacy codebases
252
Legacy codebases
Combined lines of code
99M
Combined lines of code

What it contains

The top entries by volume, with the long tail collapsed into a single figure.

DSA Codebase - by language

Language

  • Java5.1M20%
  • C#5.1M20%
  • C++4.9M19%
  • JavaScript4.5M18%
  • Python4.2M16%
  • Other (PHP, C)990K3%

Legacy Codebases - by industry

Industry

  • Media, Content & Specialized SaaS70M73%
  • HR & Workforce Management6.7M7%
  • Business Operations Platforms3.2M3%
  • Industrial, Manufacturing & Sustainability2.6M2%
  • Education & EdTech2.2M2%
  • Construction & Property Technology2.1M2%
  • Other (8 industries)8.6M8%

Record schema

Every field a delivered record carries, its type, and an example value.

dsa

FieldTypeDescriptionExample
problem_titlestringProblem name.Shortest Path in a Binary Weight Graph
topicstringProblem category.DSA
languagesstring[]Languages with a verified solution.["cpp","java","python","csharp","javascript"]
solution_linesintegerLine count for a given language solution.67
solution_tokensintegerToken count for a given language solution.535

Scroll to see all columns

legacy

FieldTypeDescriptionExample
repository_namestringRepository identifier.gibbon-android-app
industrystringIndustry classification from the source taxonomy.Education & EdTech
languages_usedstring[]Programming languages present in the repository.["Java","JavaScript","Kotlin","HTML","CSS"]
total_commitsintegerCumulative commit count in the git history.5163
total_filesintegerFile count in the repository.407
development_span_monthsnumberMonths from first to last commit.88
source_licensestringOSI-approved license the repository was verified under.MIT

Scroll to see all columns

Sample records

Real rows, exactly as delivered. Copy them and check them.

Specimen · Coding DatasetDSA problem record
problem titleShortest Path in a Binary Weight Graph
topicDSA
cpp lines67
cpp tokens535
Verified
DSA problem record · 1 shown
[  {    "problem_title": "Shortest Path in a Binary Weight Graph",    "topic": "DSA",    "languages": [      "cpp",      "java",      "python",      "csharp",      "javascript"    ],    "cpp_lines": 67,    "cpp_tokens": 535  }]
Legacy codebase record · 1 shown
[  {    "repository_name": "gibbon-android-app",    "industry": "Education & EdTech",    "languages_used": [      "Java",      "JavaScript",      "Kotlin",      "HTML",      "CSS"    ],    "total_commits": 5163,    "total_files": 407,    "development_span_months": 88  }]

Provenance and rights

Sources, acquisition method, and the basis on which the material is held.

Source types
  • Public GitHub repositories
  • Independently authored DSA problem-solution pairs
Acquisition
Legacy Codebases are selected via GitHub API screening for license clarity, commit-history depth, and industry relevance. DSA Codebase problems and solutions are independently authored and execution-tested.
Rights basis
Legacy Codebases retain their original OSI-approved license, tracked per repository. DSA Codebase pairs are held under direct ownership.
Attribution fields
  • Repository name
  • Source license
  • Industry classification
License posture
Legacy Codebases redistribution follows the constituent repository license; DSA Codebase is provided under a custom license granted per engagement.

Quality pipeline

Every record passes these stages in order. Each stage states what it removes.

  1. Repository and problem intake

    Pulls candidate repositories via the GitHub API; authors DSA problem-solution pairs to a fixed rubric.

    Inactive, archived, or low-signal repositories.

  2. License audit

    Confirms an OSI-approved or permissive license before inclusion.

    Repositories with restrictive or unclear licensing.

  3. Execution verification

    Runs every DSA solution against its test cases per language.

    Non-compiling or failing submissions.

  4. Duplicate detection

    Compares repository full name and normalized problem title.

    Duplicate entries.

  5. Static security scan

    Scans dependencies and code patterns against known vulnerability signatures.

    Files flagged for known vulnerable patterns.

Contamination screening

Named benchmarks checked for overlap, and the method used to check them.

Benchmarks checked
HumanEval, MBPP, SWE-bench, LiveCodeBench
Method
Function-signature and docstring matching against benchmark problem sets, with manual review of high-similarity flags.

Delivery

Formats, access mechanisms, and how revisions are published.

Formats
  • JSONL
  • Parquet
  • Arrow (IPC)
Mechanisms
  • S3 pre-signed URL
  • Private Hugging Face repository
Versioning
Immutable dated snapshots, referenced by release tag.
Update cadence
Quarterly refresh.
Access model
Evaluation copy on request; full access under a signed data agreement.

Known limitations

What this dataset does not cover. Read this before you evaluate it.

  • DSA solutions are written for correctness and clarity, not production-grade performance or style.
  • Legacy Codebase industry classification follows the acquisition-time taxonomy and is not re-verified against current company operations.
  • Concentrated in Media, Content & Specialized SaaS by line count; other industries contribute a smaller share of Legacy Codebase volume.
  • DSA Codebase language coverage (seven languages) does not include lower-resource or systems languages such as Rust or Go.

Request access to Coding Dataset

We share sample records on request. Tell us your training stage and intended use and we will send an evaluation copy where the use fits.

Request sample records