Practical overview
When it fits
Consult it when describing a weakness found in Solidity code or preparing classification-based security-analysis training, while checking current sources for the relevance of existing entries.
Who it is for
- Smart-contract security reviewers standardizing findings about Solidity code.
- Educators and tool developers using weakness classifications and test cases to support security analysis.
Documented uses
- Find a shared identifier and description for a Solidity weakness.
- Map audit findings to a consistent smart-contract weakness taxonomy.
- Use registry test cases in security-analysis training.
Requirements & limits
The repository is public and specifies an MIT license.
- The registry implements the EIP-1470 classification scheme and is loosely aligned with CWE terminology and structure.
- Its scope is Solidity code; smart-contract-adjacent code such as wallets is outside the registry’s stated coverage.
- The project says it is no longer actively maintained, with no new entries added since 2020; existing content should be checked against external sources.
Check current requirements in the official documentation. Source-based guidance does not mean OpenViST has run or independently tested this project.
Classify a Solidity smart-contract weakness with the SWC Registry
Use the registry’s weakness taxonomy to describe a security issue identified in Solidity code.
Before you start
- A security issue in Solidity smart-contract code to classify.
Steps
Consult the SWC Registry for a relevant weakness classification.
Use the weakness identifier and description to record the issue in a consistent vocabulary.
Check external sources to clarify whether the existing registry content remains relevant.
Expected outcome
A Solidity security finding described using the SWC Registry’s shared weakness-classification vocabulary.
Guide limitations
- The registry is no longer actively maintained, and new entries have not been added since 2020.
- The registry covers weaknesses identifiable in Solidity smart-contract code, not weaknesses in adjacent code such as wallet code.
- Existing content may require clarification from external sources.
Sources & review
Source record details
- Source availability
- Active
- Sources checked
- 14 October 2026
- Original website title
- SmartContractSecurity/SWC-registry · Official homepage title · retained in its source language
Related options
EEA EthTrust Security Levels specification — The repository points to this maintained Solidity-focused specification and says the vulnerabilities in the SWC Registry were incorporated into its version 1.
Smart Contract Security Verification Standard (SCSVS) — The repository describes this as a maintained, more general development guideline for security testing and remediation across a broad range of projects.