OpenViSTAI · Agents · Blockchain · Crypto
Submit a project
Menu
Developer Tools

SB Curated

SB Curated is a research dataset of Solidity smart contracts annotated with vulnerability categories and reported vulnerable lines. It provides reference cases for evaluating automated smart-contract analysis tools; it is not itself an analyzer or blockchain network.

Explore the practical guide ↓

Independent OpenViST project profile, based on linked sources.

SB Curated — OpenViST project profile in Developer Tools.
OpenViST project illustration. See the linked sources for product details.
Understand the project

Practical overview

When it fits

Use SB Curated when an evaluation needs Solidity examples with vulnerability labels and reported line locations, especially for comparing analysis tools.

Who it is for

  • Researchers comparing automated Solidity vulnerability analyzers.
  • Developers or research teams assembling labeled contract cases for security evaluation.

Documented uses

  • Compare analyzer findings against annotated vulnerability examples.
  • Organize evaluation cases by vulnerability category.
  • Contribute a contract or revise an annotation using the repository’s stated contribution process.
Before you choose

Requirements & limits

The repository is public and identifies its license as Apache-2.0. The README states that included contracts retain their original licenses.

  • The dataset covers categories such as reentrancy, access control, arithmetic errors, unchecked low-level calls, denial of service, bad randomness, front running, time manipulation and short addresses.
  • Annotations include source and author metadata, reported vulnerable line numbers, and category comments.
  • The dataset provides evaluation material; running analysis requires an analysis tool or framework.
  • Repository metadata lists Apache-2.0, while individual included contracts retain their original licenses.

Check current requirements in the official documentation. Source-based guidance does not mean OpenViST has run or independently tested this project.

Source-based practical guide

Inspect SB Curated contracts and vulnerability annotations

Use the dataset’s DASP-organized Solidity contracts and report comments as labeled material for security research.

Before you start

  • Access to the public SB Curated repository.

Steps

  1. Choose a vulnerability category from the repository’s DASP-organized dataset, such as reentrancy or arithmetic.

  2. Inspect the Solidity contracts in that category.

  3. Read the annotations: file comments identify source, author, and reported line numbers; marked lines use the form // CATEGORY.

  4. Use the annotated contracts as research or evaluation material for automated analysis tools.

Expected outcome

A set of Solidity contracts organized by vulnerability category, with annotations identifying reported vulnerable lines.

Guide limitations

  • The dataset is a research corpus, not an automated analysis tool.
  • Contracts were obtained from public websites or Etherscan and retain their original licenses; the README states the Apache-2.0 license applies to other files.
Documentation 1 ↗
Source-based practical guide

Propose an annotated contract for the dataset

Prepare a contribution that follows the repository’s documented process for adding a contract or updating annotations.

Before you start

  • A new or existing Solidity contract and its vulnerability annotations.
  • A GitHub pull request submission.

Steps

  1. Add a contract or update an existing annotation using the repository’s documented annotation style.

  2. Update the root vulnerabilities.json file.

  3. Run scripts/get_vulns_lines.js to update the vulnerability line information.

  4. Optionally format the JSON file with the command below.

    Documented command
    python -m json.tool

  5. Submit a pull request with the new information.

Expected outcome

A pull request containing the contract or annotation changes and an updated vulnerability index.

Guide limitations

  • The repository welcomes contributions, but acceptance or merge is not guaranteed.
  • Contracts retain their original licenses; the README says the Apache-2.0 license applies to other files.
Documentation 1 ↗
Evidence and transparency

Sources & review

Official repository ↗
Source record details
Source availability
Active
Sources checked
14 October 2026
Original website title
smartbugs/smartbugs-curated · Official homepage title · retained in its source language
How we review sourcesSuggest a correction